Page 1 of 1

TUniQuery, ExecSQL vs Open/Close

Posted: Mon 21 Jul 2014 12:25
by DerCarstenUK
Hi,

I've just started with UniDAC (test version so far). From what I've seen, a nice product!!

I've got a few 'newbee' questions:

1) What is the difference between the
a) ExecSQL
b) Execute
c) Open/Close
procedures?

2) Instead of dropping components on the form, I prefer to create them myself. I found out, that I cannot free or destroy the TUniQuery object without causing an exception. It works, when I create it with a TUniComponent object as its owner. The TUniQuery object will then be free'ed when the TUniConnection object is free'ed. Is this as intended?

Maybe the answers are obvious, but I couldn't find anything in the docs, which might have answered the above.

Regards

Carsten

Re: TUniQuery, ExecSQL vs Open/Close

Posted: Mon 21 Jul 2014 13:12
by AlexP
Hello,

There is no difference between ExecSQL and Execute methods, they are added to simplify migration from other components. The Open method will work only when a SQL statement (or a function/procedure) returns RecordSet (Cursor), otherwise, the Open method will return an error.
A similar issue occurred when developing mobile applications and is now fixed. The fix will be included in the next UniDAC version.

Re: TUniQuery, ExecSQL vs Open/Close

Posted: Mon 21 Jul 2014 13:43
by DerCarstenUK
Hi Alex,

thanks for the swift response!

Re 2), I forgot to mention, that this occurred on IOS, not on Win32.

All understood. Thanks!

Regards

Carsten

Re: TUniQuery, ExecSQL vs Open/Close

Posted: Tue 22 Jul 2014 07:33
by AlexP
Yes, this problem is already fixed for mobile platforms, we'll try to release a new build with this fix by the end of the month.