Andreas Probst wrote:
Please read between the lines:
On 2 Aug 2004 at 9:46, Oliver Zeigermann wrote:
James Mason wrote:
I think a vote would be good. Since with the RDBMS stores a read request
can lock the database it should probably happen in a transaction. I'm
still learning the intricacies of transactions, though, so don't take my
word on it :).
Not quite sure what you mean here. If the read request is not part of a
transaction the locks will only be there for the duration of this single
read statement, not for the duration of the whole transaction. This is
better, isn't is?
With implicit transactions there will be database transactions
started automatically. These will last until the
Connection.close().
Actually one should avoid closing connections. With a connection
pool a connection will never be closed so the transaction will
last until a commit or rollback.
Not quite sure what your intention is here. Could you please clarify?
Thanks,
Oliver
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
