|
Archives of the TeradataForumMessage Posted: Wed, 15 Jun 2005 @ 07:32:04 GMT
The V2R5 manual set has an entire volume on International Character sets. I would encourage you to have a look at that. The document number (for V2R5.0) is B035-1125-122A Failing that, if you like to live on the wild side and wish to take a short cut, try looking at the "Data Definition Statements" (i.e. the one describing create table). Turn to the "Character Set" clause and you will see it lists UNICODE. You could even try creating a table as per the following and see if it works for you. create table testing (c1 varchar (10) character set unicode); I hope this helps Glenn Mc P.S. In developing a couple of globalised applications (in VB), there are more considerations than simply can the database support MBCS. I don't know if you use any indicators (eg. Y/N, T/F, status values etc). If you are, you might find it easier to convert some of these to numerics. For example, 1/0 for yes/no, true/false, and other values for status codes. By doing this I mean convert to integer data type, not simply store numbers in a character field. You might find that you will save yourself from experiencing some headaches by doing this sooner rather than later.
| ||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||
Copyright 2016 - All Rights Reserved | ||||||||||||||||||||||||||||||||||||||||||||||||
Last Modified: 15 Jun 2023 | ||||||||||||||||||||||||||||||||||||||||||||||||