Hi Jon.Do you have some write where somebody explain why identity is so good ?
Using ORM identity is not recommended because the only way to know the ID of the entity is writing the entity itself in a safe state and hopefully inside a transaction and, after the INSERT INTO, read, in some way, the result to know the ID. There are various other reasons... for example try a migration. Take a look here http://nhusers.googlegroups.com/web/WhitePaper_Mapping_Objects_To_Relational_Databases.pdf Please if you find something where somebody explain why identity is so good instead a simple int, let me know. 2008/11/7 Jon Palmer <[EMAIL PROTECTED]> > I've seen this comment before but never found a good explanation of why > identity is not recommended. Is there a good write up of the problem and > what the various solutions are? > > > > Thanks > > Jon > > > > *From:* [email protected] [mailto:[EMAIL PROTECTED] *On > Behalf Of *Fabio Maulo > *Sent:* Friday, November 07, 2008 8:28 AM > *To:* [email protected] > *Subject:* [nhusers] Re: Second Level Cache on Insert > > > > 2008/11/7 Ayende Rahien <[EMAIL PROTECTED]> > > And, in general, it is not recommended to use identity for other reasons. > > usage of batching is one good reason > > > > It is an hard and heavy battle to fight. > > > > -- > Fabio Maulo > > > > > -- Fabio Maulo --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
