I'll get back to you regarding 1 and 2.
Regarding 3' this is caused by new functionality related to it seems you need to acquaint yourself with the use_sql_quoted_identifiers deployment parameter, mentioned in my original post as one of the highlights of this release .
This parameter, specified in the configuration/context file, and defaulting to false if not specified, controls how Tersus accesses database schema objects which have non-latin or other "problematic" characters in their names. If set to false then names are sql-ized (i.e. all such chars are replaced with underscores), whereas if true, names are left as-is and surrounded by quotes when referenced.
So, you'll need to add
to your Configuration.xml (in studio) or context file (in deployment).
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
