The docs on this are a little thin.. so I have a couple of questions: 1. should I use the migrate command or should I install alembic?
2. after running 'migrate' and creating a migrations folder I run 'migrate script --repository=migration initial_schema' and had the 001_initial_schema.py file created. (empty) 3. what is actually the correct way to handle db changes: should I change the *model *first and then import the model into a *migration script* and there add a column/table? or Vice Versa ? or in both places together? 4. isn't there a way that tg/sqlalchemy-migrate/alembic handle those changes automatically for me? watching the scheme and 5. what does paster migrate do? couldn't find it in the docs but I guess it supposed to acually run the migration script. when I try to run 'paster migrate script' I get a 'Unable to read config file or missing sqlalchemy.url in app:main section' but since I'm using a multiple db configuration I have sqlalchemy.first.url and sqlalcehmy.second.url. how can I adapt the paster migrate to accept this? 6.. for using alembic - I saw in alembic docs there is a pylons connector, does it work with turbogears too? I'm using tg 2.1.3 with two db (one an mssql which I can't change the tables and scheme and mysql for the rest of the work, I need migrations only for the mssql). the db exists already I'm complete newbie with db migrations (discovered them while doing a Django project and then searched back in my favorite python framework) so I would really appreciate a detailed explanation thanks! -- You received this message because you are subscribed to the Google Groups "TurboGears" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/turbogears?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
