I'm unsure if I get you correctly: First you speak about transaction isolation level, but at the end you ask about "distinct transaction".
According to the reference, a distinct transaction is used: http://nhforge.org/doc/nh/en/index.html#mapping-declaration-id-hilo /Oskar 2010/2/2 [email protected] <[email protected]>: > > Any ideas ? > > On Jan 29, 12:08 pm, "[email protected]" <[email protected]> wrote: >> 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,hilotable, 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 thehilogetting >> 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. > > -- 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.
