Doesn't that still serialize all updates requiring access to that sequence?
If you used it within a transaction it would also have implications with other transactions using that "sequence" especially in a rollback situation. In the context of AOLServer you could minimise the impact of these problems by initialising a totally seperate pool of db connections just for this "sequence" manipulation proc. This could decrease performance though - especially if there is network latency between aolserver and the database. I'd prefer my enterprise database not to decide that it would be a good idea to allow NULL = NULL to evaluate as true by default, but now I'm getting off topic ;) -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
