Hi Paul Where would I put the logic for constructing the text in the sql-update/insert elements? It's database-dependent. It also doesn't have to be used with stored procs, so it will have to be flexible enough to support other conventions in the future.
Another question is whether FNH should add good cross-db support for SPs before NH even does. Are there other examples of FNH adding features to plain NH other than the fact that mapping can be automated/convention-based/simplified? Is such a feature feasible or even desirable? Using SPs with NH is a bit of an antipattern, but iBATIS maps to hand-written SQL queries with relative success so perhaps it isn't such a bad idea. If it makes sense I may decide to start work on this. But progress will be slow because I'm swamped with work at the moment. So, the tl;dr version: 1. Is there other database-dependent logic in FNH? 2. Is it OK for FNH to add features that NH doesn't directly support? 3. Does such a feature make sense at all? Am I the first to suggest it? Regards Kevin -- You received this message because you are subscribed to the Google Groups "Fluent NHibernate" group. To post to this group, send email to fluent-nhibern...@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.
