The plan after 1.0 is to change dm-migrations in various ways. Dan already described most of it in http://groups.google.com/group/datamapper/browse_thread/thread/658433267df4475
Something that I think wasn't mentioned in that thread, is that we plan to refactor the SQL generation code, so that it will be easily possible to implement a proper #to_sql method for queries at least (and I would think also for the DDL parts). To be honest, I haven't yet thought about the need / possibility to have a way to really export the raw SQL/DDL .. but that should be reasonably easy with that new code in place. We'll see if it ends up in dm-migrations itself, or if it could also be implemented in another plugin (haven't thought much about that yet obviously) cheers snusnu On Tue, Jun 1, 2010 at 10:47, Freak <[email protected]> wrote: > On Monday 31 May 2010 22.35:24 MrRuby wrote: >> is there a possibility to export the generated table DDL code >> that datamapper uses to do an automigrate? > Pretty simple and ugly: Enable debug logger and copy/paste the SQL output if > you run DataMapper.auto_migrate! > > -- > You received this message because you are subscribed to the Google Groups > "DataMapper" 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/datamapper?hl=en. > > -- You received this message because you are subscribed to the Google Groups "DataMapper" 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/datamapper?hl=en.
