On Sat, Oct 22, 2011 at 1:53 PM, Martin Schreiber <mse00...@gmail.com> wrote: > On Saturday 22 October 2011 17.23:38 Marcos Douglas wrote: >> On Sat, Oct 22, 2011 at 11:21 AM, <michael.vancann...@wisa.be> wrote: >> >> DBComm.SQLTransaction.StartTransaction; <-- Fails here with >> >> "transaction already active" >> > >> > Correct. The default transaction is made active after connecting. >> > You should call StartTransaction on this transaction only after a commit >> > or rollback. >> >> I also found this problem when I migrated from Zeos to SQLdb. >> Only SQLdb works in this way. IMHO, it not make sense. >> For automatic transactions, the user can define AutoCommit=True If it >> is False, I can call StartTransaction BEFORE the Commit. That is the >> way that all libs work. >> > That means there are different transactions for reading and writing? MSEgui > has this option too. But what if reading and writing should be in a single > transaction?
I'm talking about transactions for writing. Marcos Douglas _______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
