Hey Bruce, Ok, I've figured out the source of the bug we're seeing, but I'm not sure how to reproduce it in a test. Here's what we're seeing:
On line 47 in satchmo.apps.livesettings.models the cache-miss logic is calling 'loading.app_cache_ready()' In our case that method is always returning false. Thus, the database-value is never loaded, and Satchmo creates a new Setting object in it's place. When this new setting is saved to the db, it's triggering the IntegrityError. I dug into the django.db.models.loading module a bit, and it appears that a module/app someplace else in our codebase isn't loading properly, and thus app_cache_ready() never finishes correctly. That explains why we're seeing the problem in development but the tests pass. So, I'm assuming this isn't a Satchmo problem directly. However, this _is_ the only side effect we've seen of whatever underlying problem we're dealing with. The site works fine-as-is otherwise. I'm going to keep digging, but I thought I'd document what we've found to-date. Our temporary fix was to remove the call to 'loading.app_cache_ready ()' for now. Everything is working as expected. Just out of curiosity, what's the benefit of using app_cache_ready()? Thanks for the help and the great product! -Brian --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
