#9302: postgresql: currval of sequence is not yet defined in this session: fix
---------------------------------------------------+------------------------
Reporter: b...@erentil.net | Owner: nobody
Status: reopened | Milestone:
Component: Database layer (models, ORM) | Version: 1.0
Resolution: | Keywords:
Stage: Unreviewed | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Changes (by RaceCondition):
* status: closed => reopened
* resolution: invalid =>
Comment:
I ran into the exact same problem. So Django is assuming the ID sequence
of a model's table is appname_model_id_seq, but should Django actually
make this assumption? What if I'm using a legacy schema? What if I just
ran RENAME TABLE and didn't rename the ID sequence? Are these scenarios
not legitimate?
Shouldn't Django just introspect the DB schema to know exactly which ID
sequence to use for a model?
--
Ticket URL: <http://code.djangoproject.com/ticket/9302#comment:3>
Django <http://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
-~----------~----~----~----~------~----~------~--~---
