I'm afraid we need to update and insert PhotoStatus rows - we're using NH to provide a sane domain model over a criminally twisted DB schema and apart from this little edge detail, so far it's going rather well...
The alternative is to map PhotoStatus as a component or associated entity and then manage the abstraction in our own code, but a join mapping would be far cleaner and consistent with what we've done elsewhere. Thanks, -D- On 2 June 2011 13:20, James Gregory <jagregory....@gmail.com> wrote: > I'll do some digging. > > In the meantime, do you need to insert into this table? (please say no). If > not, you could use a view to get around the problem. I'll try find a proper > solution. > > -- > You received this message because you are subscribed to the Google Groups > "Fluent NHibernate" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/fluent-nhibernate/-/ZnlGOFRTeHFDN29K. > To post to this group, send email to fluent-nhibernate@googlegroups.com. > To unsubscribe from this group, send email to > fluent-nhibernate+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/fluent-nhibernate?hl=en. > -- You received this message because you are subscribed to the Google Groups "Fluent NHibernate" group. To post to this group, send email to fluent-nhibernate@googlegroups.com. To unsubscribe from this group, send email to fluent-nhibernate+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/fluent-nhibernate?hl=en.
