[fpc-devel] PostgreSQL SQLdb transactions

Chris Dryburgh cdryburghca at netscape.net
Thu Nov 6 15:43:03 CET 2014

On 06/11/14 01:31 AM, Martin Schreiber wrote:
> On Wednesday 05 November 2014 19:19:41 Chris Dryburgh wrote:
> [...]> run together. It is also read-only transaction idiot proof which is a
>> good thing. Michael's approach of allowing for closing a transaction
>> without closing a still in use dataset looks like a better approach. It
>> will still cause issues for users "that don't like and often even don't
>> know transactions".
> Just for clarification, the mentioned MSEgui dataset "disconnect"/"reconnect"
> functionality provides that possibility. Activate
> tmsesqlquery.contoller.options "dso_offline" and it will be handled
> automatically.
> Martin
> _______________________________________________
> fpc-devel maillist  -  fpc-devel at lists.freepascal.org
> http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
I understand that but I don't think your approach allows for a series of 
read-only queries to be run in a single transaction batch. It is a 
simple trade off of security vs possible performance gain.

More information about the fpc-devel mailing list