First of all, thanks for quick response! Indeed, creating separate entity would solve the problem, but it's so common scenario that I would end up creating new entitiy for each page with editing functionality. I cannot believe that it's a way all those people using nhibernate with asp.net follow, do they really? Also I have tools for autogenerating entities from db, so handcoding some of them would be expecially annoying - I always thought that the power of Hibernate allows to mostly use 1-1 entity - table mappings and get all needed combinations using only those entities.
Basically it means that I should have as many entities for one table as there are ways to present those data. Fabio, what did you mean by your comment? That loading before updating is needed anyway for optimistic locking? If so, shouldn't it be implemented by lower layer? thanks HP On Oct 12, 6:07 pm, "Fabio Maulo" <[EMAIL PROTECTED]> wrote: > 2008/10/12 Ken Egozi <[EMAIL PROTECTED]> > > > I'd say it's a matter of context. > > so, in the context of reordering instances of Entity, only the ID and > > Ordinal fields are interesting. > > so I'd map EntityForReorder to the same table, with only the ID and ordinal > > fields, and use it to update. > > Optimistic-locking ? > > -- > 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 -~----------~----~----~----~------~----~------~--~---
