One scenario: A user post an order, and receives as a confirmation, an order number (which must be unique and so, it's my primary key). It would be akward to see something like:
"Your order is: 3F2504E0-4F89-11D3-9A0C-0305E82C3301" On Wed, Apr 15, 2009 at 1:56 PM, Greg Young <gregoryyou...@gmail.com> wrote: > > Why do you want human readable keys? > > On Wed, Apr 15, 2009 at 12:53 PM, caiokf <cai...@gmail.com> wrote: >> >> Hi, >> >> Which approach do you guys suggest to handle Primary Keys in an >> occasionally connected system? >> >> In my understanding, the options are: >> >> - GUIDs/UUIDs : which present a non-human readable key, which I want >> to avoid. >> - AppID, ID: difficult to mantain the AppID for all the clients, and I >> think it kind of polute my domain. >> - Some sort of Primary Key Pool: how could I integrate that with >> NHibernate in a (most) transparent way (as possible)? >> >> If someone has some other suggestion or stories about that matter, it >> would be very helpfull. >> >> Thanks, >> Caio >> > >> > > > > -- > It is the mark of an educated mind to be able to entertain a thought > without accepting it. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to nhusers@googlegroups.com To unsubscribe from this group, send email to nhusers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nhusers?hl=en -~----------~----~----~----~------~----~------~--~---
