Hi Rory, Something I discovered yesterday is my own environment is that I was coupling my Migrations to my ORM mappings, which I decided was a pretty bad idea (in general - migrations should be immutable but mappings can change). I'd therefore say, in my opinion, you don't have a choice but to write 'nasty sql statements' to insert/migrate data.
On Apr 16, 11:41 am, Rory Fitzpatrick <[email protected]> wrote: > Apologies if this has been covered before, searching didn't throw > anything up. > > I'm wondering how one would manage migrating existing data using > Migrator.NET? > > Looking at ITransformationProvider, the only way I can see to do this > is with the ExecuteNonQuery() or Update() methods. The Update() method > seems to be mainly useful for inserting default data, whilst > ExecuteNonQuery() could in theory be used to change existing data but > I'd have to write lots of nasty SQL (which is what I'm trying to avoid > by using an ORM and a migrations framework). Is there a better way? If > not, what plans or suggestions do you have for this? > > Cheers > Rory --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "migratordotnet-devel" 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/migratordotnet-devel?hl=en -~----------~----~----~----~------~----~------~--~---
