Check the QuoteValue setting in the Insert/Update actions. If that is true an empty string should insert/update as '' not NULL.
From: Andrej Popovic [mailto:and...@workflowengine.co.uk] Sent: Tuesday, October 03, 2023 6:25 AM To: terascript-talk@terascript.com Subject: TeraScript-Talk: The effect of ANSI99SQL=true Hi everyone A customer had recently upgraded to TeraScript 7 and had to set the server configuration variable ANSI99SQL to TRUE so that TeraScribe actions generate the correct SQL ANSII joins. However, either the TS7 itself or the ANSI99SQL setting caused a problem with handling empty strings in the INSERT and UPDATE actions. With previous versions of TS an empty string would generate an empty string SQL value assignement, now it is translated into NULL. Consequently we have a database with many NULL values where we normally expect blank strings. This is causing problems with legacy code. Is there any way to force TS7 globally to stop converting empty strings into NULLs in actions with ANSI99SQL=true? Please note that custom SQL does not have this problem. We are looking for a solution that would avoid having to hand-revise dozens of legacy TAF files. Many thanks for any responses in advance! Andrej Popovic https://workflowengine.co.uk _____ To unsubscribe from this list, please send an email to lists...@terascript.com <mailto:lists...@terascript.com> with "unsubscribe terascript-talk" in the body. ---------------------------------------- To unsubscribe from this list, please send an email to lists...@terascript.com with "unsubscribe terascript-talk" in the body.
