Michael Van Canneyt wrote:
Then I don't see why multiple concurrent transactions are useful ? The
user can only do one thing at a time anyway, right? :-)
Didn't you implement threads ? ;-)
Not if you make e.g. some reports in the background, using threads.
Hmm I didn't expect multiple transactions on one connection to be thread
safe.
For server apps, multiple transactions in a connection are a must.
My apps at work depend on it: one connection to the database, and at least
1 transaction per user...
The 'middle' tier, you mean ? Why is the single connection a must ?
Micha
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
