It seems , getting the hi value from generator table occurs in the
first transaction level that we create from our application which
sounds a bit dangerous to me.

Suppose two different applications start at same time,both of their
first transactions' will take some long time.
If transaction A updates, hilo table, then transaction B will wait A
to finish  to get its next value assuming both transactions are read
committed. Am I thinking wrong? I have a feeling the hilo getting
process should be done in a distinct transaction.

-- 
You received this message because you are subscribed to the Google Groups 
"nhusers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/nhusers?hl=en.

Reply via email to