#33737: DB queries with using() not consistent/correct
-------------------------------------+-------------------------------------
Reporter: Stephen | Owner: nobody
Brown |
Type: Bug | Status: new
Component: Database | Version: 3.2
layer (models, ORM) |
Severity: Normal | Keywords: using
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
I've got a case where I carefully operate on a database with the ORM
creating objects (using "objects.using", and in transactions with "using="
consistently set for the decorator arg) - and then querying them in the
same session. When I connect with "using" set to non default - the query
operations on the created objects do not return any results. It works fine
when "using" is set to 'default'. The other database, to confirm it wasn't
a database configuration issue, I set it so that the config for "default"
pointed to that database, and again it worked fine.
I also removed transactions, to simplify any complexity, and it was still
an issue.
I tested this is also an issue with 4.0.4, though I was using 3.2.13
initially.
--
Ticket URL: <https://code.djangoproject.com/ticket/33737>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070180f1f798e1-ebc90beb-2adc-463f-9012-02bb34b76d0f-000000%40eu-central-1.amazonses.com.
