[fpc-pascal] SQLDB: how to use TSQLTransaction

Xiangrong Fang xrfang at gmail.com
Sat Apr 11 03:53:34 CEST 2015

Hi All,

Sorry that I don't know if SQLDB belongs to fpc or lazarus, so I posted to
both lists.

I am confused about the use of transaction in SQLDB. I tried to use in in
my non-gui app. Here is the code:

function TPortfolio.ConfirmTransaction(id: Integer): Boolean;
  with qr do begin
    SQL.Text := Format('UPDATE records SET status=%d WHERE id=%d AND
      [TR_SUCCESS, id, TR_PENDING]);
    WriteLn('Confirming: ', id, ', affected: ', RowsAffected);
    //WriteLn('Confirming: ', id, ', affected: ', RowsAffected);
    Result := RowsAffected > 0;
It seems that I must assign a TSQLTransaction object to the TSQLQuery
object, otherwise it doesn't work. I also found that without call
tr.Commit, the ExecSQL will not take effect, at least for INSERT

In the above function, I found the first WriteLn will output rows-affected
as 1, and the 2nd (after tr.Commit) will output rows-affected as -1!  I
then commented out the tr.Commit; statement, it STILL worked.

Now my questions are:

1. How to control the use of transactions in SQLDB? Sometime I do NOT want
transaction, but want the DDL/DML statement to be executed immediately.
Why sometime SQLDB's ExecSQL won't take effect if not followed by a Commit?
BTW, I tried to set tr.Active to true/false before execute the sql, but it
seems not making a difference?

2. What is the meaning of -1 as returned by RowsAffected?


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freepascal.org/pipermail/fpc-pascal/attachments/20150411/9b3456ed/attachment.html>

More information about the fpc-pascal mailing list