Thanks for the fix, Chris. That issue had caused me some grief. On Mar 15, 10:11 pm, Chris Moffitt <[email protected]> wrote: > 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/BackwardsIncompatible... > > 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]. For more options, visit this group at http://groups.google.com/group/satchmo-users?hl=en.
