Hi Cory, I haven't been checking the list for awhile. My group and Armin put in the oracle style sequencer for SQL Server, because I had too many problems with the regular sequence manager on multiple app servers and didn't want to use the sql server sequence approach. The stored procedure hangs off the current transaction (it doesn't commit itself), so if you roll back the transaction, it shouldn't commit the sequence. I'm still using the original pre-checkin prototype with 0.9.7 in production. It should be the same except for the class name and table it uses. IMO it's much easier that way to make your app portable between databases.
Ryan -----Original Message----- From: Cory L Hubert [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 15, 2003 2:34 PM To: OJB Users List Subject: MS SQL Server Sequence Solution My Dev group is planning on implementing the MSSQL sequence solution describe here http://db.apache.org/ojb/sequencemanager.html#Oracle-style%20sequencing One of our developers raised a concern about using this method within transactions. What happens during a rollback? For example. One process gets the next val. Let's say it returns 10, and another process get's 11. What happens to the OJB_NEXT_VAL table if the transaction (the one that got 10) was rolled back? Also on a side note. Is there anyone developing a MS SQL Server Sequencer? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
