[Lazarus] What is a TSQLTransaction and why do I need one?

Michael Van Canneyt michael at freepascal.org
Fri Dec 10 10:58:53 CET 2010

On Fri, 10 Dec 2010, Mark Morgan Lloyd wrote:

> Joost van der Sluis wrote:
>>> Since this is strictly read-only, I can't see why I need transactions, but 
>>> I obviously respect the judgment of whoever designed the architecture.
>> Well, you always need a transaction. Without a transaction, Postgres
>> will do nothing, ever.
>> I assume you are used to the fact that postgres automatically creates an
>> transaction for you. With Sqldb you have to do this yourself.
> Please excuse me for threading onto a fairly old message. In the specific 
> case of PostgreSQL, if I use SELECT * FROM pg_stat_activity to examine 
> backend state I can see that a Lazarus TSQLQuery, i.e. that has to have an 
> associated transaction object, is explicitly marked as being in a 
> transaction, while other methods of access (Delphi+BDE, PGAdmin3) are not.

This is one of the things we must still address: close the transaction after
the data has been fetched. (or rather: keep data available in case the 
transaction is closed)


More information about the Lazarus mailing list