#17241: Postgres Table not updating correctly on save with autocommit on
-------------------------------------+-------------------------------------
Reporter: anonymous | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 1.2
(models, ORM) | Resolution: invalid
Severity: Normal | Triage Stage:
Keywords: | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by kmtracey):
You say you are NOW using the Django User model. Based on your error
message, specifically My_App_users being identified in the integrity
error, not auth_users, it sounds like you originally built your models
using your own User model? Your database table for Account appears to
still be defined in a way where the DB is expecting your Account rows to
reference objects in My_App_usres, not auth_users. Note Django itself
(syncdb command) does not do any database schema migration, it simply
creates tables for models it finds that do not yet have tables in the
database. If you are making changes to the models in your Python code, you
need to either manually update the database shema to match what you have
done on the Python side, or use some tool like South to help with
automatically migrating the database schema to match changes you have made
to the Python code.
--
Ticket URL: <https://code.djangoproject.com/ticket/17241#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
