I just ran into this same problem. I think the issue is: The initial downloadable migration tries to rename the table from product_downloadableproduct to downloadable_downloadableproduct. However, anyone starting from a new install will not have a table named product_downloadableproduct. Instead, they need to execute a create table statement. When they run a syncdb, it will create all the tables that aren't in apps managed by south. Then they run the migrate command, which will run all the migrations in all installed apps. We probably need to switch this to a more standard 0001_initial.py migration.
The problem is that the app hasn't been under South's control the whole time. If south had been in use when we added the product_downloadableproduct model, then it would still be added every time, then changed, when we started fresh and ran migrations. You'd just need to make the downloadable migration depend on the migration that created the product_downloadableproduct table. To move forward, I think the easiest solution is to replace the current downloadable/migrations/0001_split.py with a downloadable/ migrations/0001_initial.py that just creates the tables. This won't allow existing users to migrate, but it would allow new stores to bootstrap correctly. The old 0001_split.py file should be kept around, because anyone updating from a previous version would need to use it instead. It is possible that you could wrap the migration in a try/ except block, making the table if it didn't exist, and then allow everyone to use the same migration. Unfortunately, the reverse migration path would be ambiguous at that point. Thoughts? Alex On May 26, 10:43 pm, mattym <[email protected]> wrote: > I am starting with a new store. > > I am unable to get clonesatcmo working on my local machine (windows), > so I've been manually copying the 'simple' and 'large' project over to > my django project directory. Sort of a hackey version based on Bruce's > technique on gosatchmo.com.From there making a couple tweaks to > settings and local_settings - to point to postgresql and email config. > And finally running a few manage.py commands: satchmo_load , > satchmo_check, syncdb, loaddata, etc... all in random order :). It > works for simple. Almost for large. > > When I syncdb I am prompted to run migrations after some initial > tables are created. Since 'simple' doesn't have 'downloadable' to > migrate it works. And all other migrations work on 'large.' > > Thanks Chris > ~Matt > > On May 26, 8:28 pm, Chris Moffitt <[email protected]> wrote: > > > Are you starting with a new store? If so, you shouldn't have to run the > > migrations to get it running. > > > Just so you know, I do think there's an issue lurking, I just haven't been > > able to find the time to recreate it yet. > > > -Chris > > > On Wed, May 26, 2010 at 8:46 PM, mattym <[email protected]> wrote: > > > Howdy - > > > > New to satchmo. Love it so far. I am using the latest version. > > > > I have the simple cart running well. > > > One issue with the large cart I am having. I am unable to run > > > migrations for "downloadable." > > > All other migrations work fine. This happens with mysql and > > > postgresql. (the mysql error led me try postgresql) > > > > The last error in the traceback is pyscopg2.ProgrammingError: relation > > > "product_downloadableproduct" does not exist. > > > > Anyone else have this problem with .0.9.1? Any ideas? > > > > Thanks, > > > Matt > > > > -- > > > 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]. For more options, visit this group at http://groups.google.com/group/satchmo-users?hl=en.
