On Thu, Dec 1, 2011 at 11:26 AM, Ludo Brands wrote:
>> MS SQLServer 2008. Lock the registers, not the server... sorry.
>>
> I guess you mean rows, pages or tables.
>
>> Ok, I can accept the TADOConnection can hiding a lot of
>> things from me, but I think it do open many transactions all
>> the ti
> MS SQLServer 2008. Lock the registers, not the server... sorry.
>
I guess you mean rows, pages or tables.
> Ok, I can accept the TADOConnection can hiding a lot of
> things from me, but I think it do open many transactions all
> the time. Using SQLServer Profiler, I can see all SQL that
> ar
On Thu, Dec 1, 2011 at 6:17 AM, Ludo Brands wrote:
>
>> I can't keep a transaction (server locked) all the time.
>>
>
> What database are you using that locks up the server when a transaction is
> started?
MS SQLServer 2008. Lock the registers, not the server... sorry.
> Oracle for example start
> I can't keep a transaction (server locked) all the time.
>
What database are you using that locks up the server when a transaction is
started?
Oracle for example starts an transaction as soon as you send an executable
SQL Statement. Opening a connection starts a transaction on the server.
The
On Wed, Nov 30, 2011 at 1:34 PM, Sven Barth wrote:
> Am 30.11.2011 15:47, schrieb Marcos Douglas:
>>
>> Hi,
>>
>> Why TSQLTransaction.Commit calls CloseDataSets?
>> Always that I call StartTransaction and Commit/Rollback and I have to
>> reopen my DataSets?!
>
> Use CommitRetaining and RollbackRet
Am 30.11.2011 15:47, schrieb Marcos Douglas:
Hi,
Why TSQLTransaction.Commit calls CloseDataSets?
Always that I call StartTransaction and Commit/Rollback and I have to
reopen my DataSets?!
Use CommitRetaining and RollbackRetaining. These don't call CloseDataSets.
Regards,
Sven
___
Hi,
Why TSQLTransaction.Commit calls CloseDataSets?
Always that I call StartTransaction and Commit/Rollback and I have to
reopen my DataSets?!
Marcos Douglas
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailma