2013/2/19 Richard Wilde <[email protected]>: > Couple of options that may/may not work > > 1. Use negative numbers (id’s) when inserting the data without NH, > this means it cannot conflict with Hilo > > 2. Use Nhibernate to insert data > > 3. Choose another identity stategy
Some more options: * Pick as id the smallest number not already used in the table. May still cause problems in theory because some already running client using NHibernate might be preparing to use this number. Algorithmically correct solution: The manual code that you use should also implement the HiLo algorithm. Either in C# or as a stored procedure (or by manual calculation). It need not be concerned with what range is allocated by the active NHibernate generator, but must allocate its own range just like any NHibernate based client would. First level cache is not related to this. It's simply the optimization system of the generator itself. Using the enhanced id generators with the pooled_lo optimizer provides an alternative with good performance (supports batch insert) but is easier to work with "manually". /Oskar -- You received this message because you are subscribed to the Google Groups "nhusers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/nhusers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
