On 3/14/06, Jorge Vargas <[EMAIL PROTECTED]> wrote:
how will you control that your controllers are in 005 but your db is in 004? I think a better aproach will be to have SVN or sometimes else, appliying this to all the project tg will be like building a versioning system on top of it which makes no sense.

I may be wrong, but IMHO database versioning has nothing to do with software versioning. My up-to-date 005 module may be used at any time with a 004 database, or even with a 002... or 001. That's life. A database versioning & migration toolkit would help to deploy newer versions; when it detects a previous version of the database, the migration kit would be automatically invoked to bring the database up to date. This is an invaluable tool to use when you're trying to keep your production version in sync with your daily builds.

--
Carlos Ribeiro
Consultoria em Projetos
blog: http://rascunhosrotos.blogspot.com
blog: http://pythonnotes.blogspot.com
mail: [EMAIL PROTECTED]
mail: [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
-~----------~----~----~----~------~----~------~--~---

Reply via email to