Sven K�hler wrote:
Hi,I am always using both _UNICODE = YES and DEFAULT_CODE = UNICODE and I haven't had any problems. I also veryfy all my code so that it works with other characters other than those in the 8859-1 character set.
is the _UNICODE=YES a good idea?
Is SAPDB's ability to handle UNICODE ready for production?
Why isn't it enabled by default?
DEFAULT_CODE is set to ASCII by default, so one wouldn't notice the presence of UNICODE until he expicitly creates a UNICODE-column.
Are all internal functions of SAPDB aware of UNICODE-colums?
May i get into troubles using UNICODE?
The big difference when acitivating unicode support is that all symbols become unicode-aware. This not only includes support for using unicode in character columns but also stores all table and column names as unicode. I.e. it's possible to name a table name with chinese characters for example.
But yes, I agree with you that _UNICODE should be default. The argument that the names of tables and columns will take twice (or 4 times if SapDB supports full unicode) the memory is not a good one, even on a huge system this wasted memory will still only be counted in tens of kilobytes.
There might be other arguments for not doing this, and I'm sure I'll be educated if I'm wrong. :-)
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
