gasolin wrote: > Right, I just add it in a minute after the 0.1 release :-P > > I finished following the versioning doc in migrate module. So the doc > should work for you, too (but I found the versioning doc didn't fit my > expectations). > > After read the doc, I found migrate is a tool which is able to > manipulate database table columns, rename tables, and you could step > back to previous table layout settings(Undo) since you host a version > control repository for the migrate code. > > Rails people require "migration" because they link to database > implicitly(they only specify the dburi in their project, such as the > case using sqlsoup in sqlalchemy), migration help them create table > from scratch and able to undo the database design. > > Since the normal usage of sqlalchemy is declaring the model explicity, > and sqlalchemy allows to create the table with create command. > "migrate" seems not the panacea in sqlalchemy as migration in rails.
It still seems highly valuable for schema modifications. Being able to attach processing code that can handle data transformations to the code that is actually making the changes to your database is pretty powerful stuff. I know I have hit plenty of little things over the last few months where I could have used it. Problem is that I need to learn at least a little bit of SA before I can start using it. -Adam --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
