CHAR / NCHAR precision is not correctly derived from DDL statements

When a CHAR or NCHAR field is modified via an ALTER TABLE or set via a CREATE TABLE statement the field's precision is automatically reset to 1 regardless of what the SQL precision dictates.