#25454: Problem using HStoreField in django shell
----------------------------------+--------------------------------------
Reporter: reichert | Owner:
Type: Bug | Status: new
Component: contrib.postgres | Version: 1.8
Severity: Normal | Resolution:
Keywords: hstorefield | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+--------------------------------------
Changes (by craigds):
* cc: craig.ds@… (added)
* status: closed => new
* resolution: needsinfo =>
Comment:
I've just had this issue. Reopening because it's marked needsinfo and I
have some :)
For us, we're using `manage.py shell` correctly, but it looks like we're
doing a database query in a silly place in our code _before_ the app cache
is ready.
That is, we're forcing a database connection, which in turn sends the
`connection_created` signal before the `register_hstore` signal handler is
registered by `PostgresConfig.ready`.
This is obviously something dumb we're doing, but it'd be nice if Django
was able to throw an error when the database connection is initialised too
early. Then we would have found this bug ages ago. Would that be possible?
--
Ticket URL: <https://code.djangoproject.com/ticket/25454#comment:2>
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 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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.34f6a45f9e53e44ee9d8ac2cef687954%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
