Subject | Re: usable characters for varchar and memos |
---|---|
Author | Ed Dressel |
Post date | 2008-01-30T18:08:31Z |
> For varachars, the set of legal characters depends on theThank you for the prompt answer.
> character set. For blobs, there shouldn't be any restrictions,
> except those implied if the blob is assumed by some application
> to be a document in a specific character set.
I am not sure how to determine the default character set of the
database. I am guessing it is NONE. Helen's book states "Character set
NONE makes no character set assumptions for text columns, storing data
exactly as entered." It would seem that NONE does not like #0,
correct? Is there a character set that would work with #0?
In reading, it seems that I could use:
alter table TableName add col_temp varchar(3) cahracter set ISO9959_2;
commit;
update table set Col_temp = cast(source_column as char(30) character
set Octets)
and then drop and re-add the source column.
But will that get me the desire results?