@PeteaA & Gunnar: Agreed. You are right, each problem is different and it needs a specific solution and guids might be good in some scenarios and they might be bad in others. As we say, the devil is in the details. Perhaps I am bit more sensitive about GUIDs because of my painful past experience working with people that used them just because. I.e. no reasoning, no thought. So, sorry, I didn't want this to be another religious war, even though sometimes is good to argue philosophically while drinking beer ;-)
I am just curious about one thing, people here seem to come from an ORM background. I am a bit surprised to see the posts against the use of identity PKs (see @Elio Batista's post and I also found other articles) for 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 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... -- You received this message because you are subscribed to the Google Groups "nhusers" group. To view this discussion on the web visit https://groups.google.com/d/msg/nhusers/-/NX4V2tu5U0AJ. 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.
