Thomas, I have no cache setup, Django is all set to default right now there is no local_settings file I have actually changed every settings file that exist for django to match my production db yet still the wrong data.
On Friday, July 11, 2014 10:30:23 AM UTC-6, Thomas wrote: > > On 7/11/14 9:27 AM, G Z wrote: > > So I tracked down an issue, whenever I change my database from > > development to production which have the same exact schema > > it still uses the data from development although my settings.py file > > is set to the production database and it even swtiches the user I have > > to log in with to the one associated with production but all of the > > data is development. > > > > I have tried running sync db and sql. Nothing seems to work I know > > this is a django ism but not sure how to fix it . > Django only knows what you tell it. > > If the production setup is really specifying the production database > (make sure you don't have a local_settings.py overriding your > settings.py values), perhaps you should check your caching setup next? > > hth > > - Tom > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/66e147de-875c-46af-be8d-1e02844f9408%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
