> the database does not support serialized transactions.
I think this would depend on the granularity of the locks within the
database. If you were using Access, again, I think this would work fine with
the default isolation level of "read committed", as the first query would
place an exclusive lock on the entire table. As a result, no one else would
be able to touch the table at all until the end of the transaction.
I only point this out to illustrate the potential complexity of
transactional processing issues - you have to know something about how your
database handles transactions to determine how you should write
transactions.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
voice: (202) 797-5496
fax: (202) 797-5444
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
