The migration script simply needs to import your existing model, and then do the steps you need to in order to migrate. So, for instance, if you're creating columns, then you issue the column create statements. Same for creating tables, dropping tables, creating indexes, etc.
On Mon, Jul 26, 2010 at 12:29 AM, waugust <[email protected]> wrote: > well...not like Rails, per se... guess its been a while, though it > seems like double work to have to define the schema in the migration > script as well as the properties in the model class... > > On Jul 25, 9:04 pm, waugust <[email protected]> wrote: > > Greetings, > > > > I'm hoping someone could help me out here... > > I'm working through the documentation available out there and it seems > > a bit sparse...I read, at least, the turbogears guide to migrations > > though it leaves me hanging a bit. > > If I'm following this correctly, I need to define the table and > > columns both in my model and in the migration script? > > Is there no paster script out there that does that (a la RoR)? > > -- > You received this message because you are subscribed to the Google Groups > "TurboGears" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<turbogears%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/turbogears?hl=en. > > -- Michael J. Pedersen My IM IDs: Jabber/[email protected], ICQ/103345809, AIM/pedermj022171 Yahoo/pedermj2002, MSN/[email protected] -- You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en.
