 |
 |
Archives of the TeradataForum
Message Posted: Sun, 08 Jul 2007 @ 19:48:37 GMT
| Subj: | | Re: Unicode surprise |
| |
| From: | | Geoffrey Rommel |
| | Only define columns as UNICODE where it is known to contain double byte characters, rather than just set all character based columns to
Unicode. | |
You should definitely do this.
| | I didn't realize the server side was UTF-16. | |
This may not be quite true. When Unicode was first added to Teradata, Unicode was a 16-bit code only, so it may be that the server will only
store characters below the 16-bit line. Since Unicode 3.0 (?), more characters have been added above the 16-bit line. These require more than 16
bits in a UTF-16 encoding, so I don't know whether the server will store them correctly or not. It's unlikely that you would ever need them,
however, unless you're working for the Library of Congress or some similarly academic enterprise (Linear B, anyone?).
| |
