+1.. .I think it is a good idea, I always wanted to have something alike. I think it will be easier if you do in two phases:
Phase 1 - add some extensibility points to the schemaupdate/dialects in nhibernate, and send a patch. - create a separated project to generate the migrations using the extensibility points Phase 2 - present the idea and patch to the nh community and let them vote if they want that feature in the core? 2011/5/18 Dru Sellers <[email protected]> > What are the chances of extending SchemaUpdate to expose the actual changes > as a model that a user could use to drive the creation of migration scripts, > such as a rails migration script. Even more so, to read in two sets of NH > mappings and then generate the difference scripts leveraging the NH > dialects. > > If I were to add this work to my fork of NHibernate would it be welcomed > back in? > > ?? > > -d > > -- > 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. > -- 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.
