Hi redrat,
Stefen's recommendation of using English characters for table and column names, is valid, since by default, when Tersus accesses the database, it converts all non-English characters (as well as Space and some other ASCII characters) to underscores (_).
There are however cases, where it is a requirement to use non-English characters, when accessing database schema. The usual case is when the application must access an existing database, which contains non-English characters in schema names, and which of course cannot be changed as it affects other systems.
Tersus supports such cases via the use_sql_quoted_identifiers deployment parameter, which prevents the conversion from taking place, as explianed in http://www.tersus.com/#Id=6207.
Of course, all this has no effect on actual data, which can contain any character supported by the database (and as far as I know, all of them do support unicode at the very least).
Regards,
David
To use the full functionality of this web site, JavaScript needs to be turned on.
For best results, use the Firefox browser..
Copyright © 2003-2017 - Tersus Software Ltd., All rights reserved. Terms of Use License Graphic design by EmaraDesign
