Unified SQL and uniConnection.ExecSQL

[FredS]

Is Unified SQL supposed to work for ExecSQL?

Because this errors out:
'{if Interbase} set generator NEXTSHAREFOLDERSID to 39 {else} Update Generators SET NEXTSHAREFOLDERSID = 39 {endif}'#$D#$A

with
---------------------------
Debugger Exception Notification
---------------------------
Project PA.exe raised exception class EIBCError with message 'Dynamic SQL Error
SQL error code = -104
Token unknown - line 1, column 1
{if'.

[ViktorV]

Unified SQL worked for ExecSQL.
To solve the problem, try to execute the following code before calling TUniConnection.ExecSQL:

Code: Select all

  if not EnableUniSQL then EnableUniSQL := True;

[FredS]

I still get the same error even if I place that code right in front of the call:

if not EnableUniSQL then EnableUniSQL := True;
v := uniConnection.ExecSQL(ASql);

TUniSQL.Execute works of course with or without that code..

[FredS]

One more thing, is TUniScript supposed to work with Unified SQL?

[ViktorV]

Please make sure you have not set the EnableUniSQL global variable to False anywhere. If it is True, please send a small sample to demonstrate the issue to viktorv*devart*com, including a script to create and fill in the test database object.
TUniScript supports Unified SQL.

[FredS]

Hi Viktor,

The Demo has been sent, turns out to reproduce in a simple demo a call to ExecProc needed to be made first.

[ViktorV]

Thank you for the information. We are investigating this behavior of UniDAC, and we will inform you about the results.

[ViktorV]

We have already fixed this issue, the fix will be included in the next UniDAC build. If you want to get this fix before the next UniDAC version is released, please provide your license number and IDE version to viktorv*devart*com and we will send you a night build.