thesamet wrote: > Fred, Thanks for making tg-migrate. It works great for me. > > The hints given by "tg-admin tg-migrate migrate help" are really > helpful to get you started quickly. > > I'd also like to know whether it makes sense to manage my changes > repository under svn?
It might make sense if you have multiple people, a lot of changes, testing/approval requirements, or something else that complicates a change development. Considering changesets are separated by directory to begin with I don't know that storing them in svn will get you much past what migrate already does. > > Migrate creates for each db version its own directory in the > repository. So one needs to do "svn add" for each db version. Creating > a new db version is quite rare, so it's okay - but I just wanted to > know if that's the way to go. AFAIK there is a Python library for svn support. It might not be too hard to wrap some portion of the migrate with code that will do 'svn add' for you. -Adam > > Best, > Nadav --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
