The fix is to not put your foreign key ids in your entities. If you need to represent that relationship in your domain then you should have a References (many-to-one) relationship there, not the foreign key. Putting foreign key ids in your entities is a big bad practice.
Your Ticket should have a HasMany(x => x.Notes) and your Note should have a References(x => x.Ticket). That's all you need. I assume you'll be saving the Ticket rather than the individual notes directly, so you'll probably want Inverse on the Notes relationship which'll make the Ticket responsible for cascading saves to each of the Notes. -- 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.
