I'd like some feedback on how people feel about the current state of the migrations feature. I've used the existing code in a project and it seems to work pretty well. That said, I haven't finished all the features that I originally wanted. The key points I've hit so far are:
- Unified DDL generation framework (no weirdness like EF where different exports generate different sql) - Migration Factory & Version Store - Usable Configuration - Fluent Builder That said, generating migrations auto-magically is turning out to be much more work than I'd originally anticipated. I think the feature is definitely achievable, I just don't have the time to do it right now. I'm proud of what the migrations code-base looks like right now. I think its the right approach. I'm also concerned about having this sit unmerged for too long. The longer I'm a fork the more work I have to keep track of the upstream. Pending some positive feedback and cleanup work I think I'd like to try to get this merged. Are people comfortable with this? -- --- You received this message because you are subscribed to the Google Groups "nhibernate-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to nhibernate-development+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
