2012/11/29 costa <[email protected]>: > performance reasons. In my case, if performance was an issue I would > probably not use nhibernate at all because I like to be in full control of
I suppose that should be understood as "ok, we use nhibernate for SomeReason - how do we get best performance from i?" But as someone mentioned earlier, it is mostly relevant if you insert a reasonable large amount of data in the same unit. > the database access. If you have a table whose PK is updated by, let's say a > HiLo algorithm, what happens if you have to have another process that that > needs to insert data in the same table, and this process doesn't use > NHibernate or even .Net? You really need to know how it works in > NHibernate... That is a drawback. HiLo is documented and not too difficult, but in my opinion the "pooled_low" generator should be the primary option, since then you don't really have to implement any "mathematics" - you just reserve a block of numbers by incrementing a counter by the amount of numbers you need. /Oskar -- 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.
