Hi chris Didn't really got time for now to dig into it but i know that django-cms project used it successfully, maybe it can help...
2010/3/16 Chris Moffitt <[email protected]> > Franck, > > Interestingly enough, I played with it a bit over the weekend. I started > with 0.9 to create the initial migration. However, once I tried to move to > the next change and create another migration, I had some trouble with the > way we set the default value for taxes as well as handling another > migration. I'm thinking we may need to use South 0.7 but I'm not 100% sure. > > The short answer is that I would like to use South but haven't quite gotten > it all working yet. If people with more experience using it do want to help > out, please do. > > Thanks, > Chris > > > On Tue, Mar 16, 2010 at 6:34 AM, franck bret <[email protected]> wrote: > >> +1 chris >> >> Have you tried or anyone tried to integrate south with satchmo... I think >> it can be util for this kind of migrations... >> >> >> 2010/3/16 Chris Moffitt <[email protected]> >> >>> I wanted to make sure everyone was aware of a backwards incompatible >>> change I just checked into hg tip. >>> >>> I changed the name of the validProducts table to valid_products. This >>> change was required because this table naming convention caused headaches >>> for several different databases. The change you need to make is simply >>> renaming the database table from product_discount_validProducts to >>> product_discount_valid_products. Example SQL is below: >>> >>> ALTER TABLE product_discount_validProducts RENAME TO >>> product_discount_valid_products; >>> >>> >>> >>> I definitely want to minimize the number of database schema changes we >>> introduce but I decided to do this one because: >>> - it was a needless headache to some users >>> - was inconsistent with the rest of our table naming standard >>> - Is easy to modify your database without losing data or doing >>> complicated sql gyrations >>> >>> You can rest assured that as we move towards 1.0 we will minimize these >>> types of changes but I felt this was one that needed to be done before we >>> lock everything down. >>> >>> As always you can read about this and other changes here - >>> >>> >>> http://www.bitbucket.org/chris1610/satchmo/wiki/BackwardsIncompatibleChangesAfter0.9 >>> >>> Thanks, >>> Chris >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Satchmo users" group. >>> To post to this group, send email to [email protected]. >>> To unsubscribe from this group, send email to >>> [email protected]<satchmo-users%[email protected]> >>> . >>> For more options, visit this group at >>> http://groups.google.com/group/satchmo-users?hl=en. >>> >> >> >> >> -- >> Franck Bret >> --------------------- >> 06 03 90 65 98 >> Fax : 09 59 95 85 96 >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Satchmo users" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]<satchmo-users%[email protected]> >> . >> For more options, visit this group at >> http://groups.google.com/group/satchmo-users?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "Satchmo users" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<satchmo-users%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/satchmo-users?hl=en. > -- Franck Bret --------------------- 06 03 90 65 98 Fax : 09 59 95 85 96 -- You received this message because you are subscribed to the Google Groups "Satchmo users" 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/satchmo-users?hl=en.
