SequentialGuid is not "far more better". It's very different, since it produces predicatable/guessable values, whereas COMBs are 80% "random".
"why this shouldn't be a part of the Nhibernate project?" Who said it shouldn't? :) OTOH, the code is there for anyone to use. It's not a hassle, really. /G 2011/9/14 kriebb <[email protected]> > Hi, > > We just filled up our data with some values... And we noticed that our > primary key index was fragemented... > > So we tought that the Guid.Comb was the way to go... > > But i've learned that actually the sequentialGuid is a far more better > way... > > I've come to this post: > > > http://www.codewrecks.com/blog/index.php/2011/05/16/using-guid-id-in-nhibernate-index-fragmentation/ > > There you can see how to use the sequential id. > > Now, I'm going to try it myself, but could someone tell me, why this > shouldn't be a part of the Nhibernate project? > > Or am I missing something? > > Thanks for discussing, > > -- > 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.
