Re: [Gnumed-devel] what about commit?

[Karsten Hilbert]

> What does that mean " real concurrent atomic transactions inside of the 
> scope of a single client connection" ?
> With one connection, I didn't think you could have more than one 
> transaction
What makes you think that ? You can just fine BEGIN COMMIT
BEGIN COMMIT. Just not concurrently.

> ( that's why the commit() operation is
> on the connection object).
This seems odd at first sight but makes sense when you
consider that you can (should be able to ?) open and
close several cursors in one connection. The commit then
simply commits all outstanding data changes.

> The semantics is that one connection object per transaction : otherwise 
> you have to start labelling the transactions per connection ;
Why would that be ? A connection is a channel through which
commands and data are sent to the database. An SQL string is a
meaningful parcel. A transaction is like a UPS truck. Either
all the parcels get there or the UPS truck crashes and no
parcels get there at all. Several UPS trucks can drive along
the channel. But not in the same spot. So, yes, you want to
get your own road. But you don't need to build a new road
every time you need it. Just send off the trucks one after the
other.

Karsten
-- 
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346