Devart Forums

Hi,

i i try to execute the following statement with TOraSQL i've got an error:

begin
execute immediate 'begin
null;
end;';
end;

The problem is that the string inside execute immediate contains a crlf and this is not allowed.

Any Chance to fix this?

Greetings
Jens

Oracle SQL syntax does not allow CRLF inside normal string constants. But in Oracle 10 you can use the alternative quoting. For example:

I know, that it's not allowed.

The problem is: you have a text editor and use the Assignment to assign the strings.

Then you got such a problem.

It's the same in your odac demo sample application.


What about changing the #13#10 to #10 using the ConvertEOL property of the session whenever a OraQuery Statement is executed.

Which other way exists to remove the #13 after a Greetings
Jens

The current version of ODAC has special code that leaves CRLF in string constants as is. We think that using the ConvertEOL option in this code can break compatibitity with previous ODAC versions.

If you want we can send you changes to the ODAC source code that will enable replacing CRLF in string constants.

Hi Oleg,

yes please.

But what about adding an additional property.

I use the components to create/execute pl/sql code in the database.
And here it is realy important to fix this crlf problematic.

And to patch your software every time is not the best solution.

Greetings
Jens

The question is: how can i assign such a peace of code to a tOraSQL.SQL property without having crlf in the sql.

Greetings
Jens

In the next ODAC build we'll add the RemoveCRInStringLiterals global variable to the OraClasses unit. You can set it to True in the initialization section of any of your units.

initialization
RemoveCRInStringLiterals := True;

I have send the changes to OraClasses.pas to your e-mail.