#27708: Relation between tables in different schemas with big names
-------------------------------------+-------------------------------------
Reporter: felipeps | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: master
Severity: Normal | Resolution:
Keywords: different schema | Triage Stage: Accepted
relation |
Has patch: 0 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* version: 1.9 => master
* needs_tests: 0 => 1
* stage: Unreviewed => Accepted
Comment:
I believe this was fixed by 69b7d4b116e3b70b250c77829e11038d5d55c2a8,
could you confirm this is the case?
Adapting the Oracle only test to also perform similar assertions on
PostgreSQL using schemas was
[https://github.com/django/django/pull/7532#discussion_r89626082 something
I proposed on the PR] but didn't enforce to avoid overloading the initial
contributor. @felipeps, is this something you could do for PostgreSQL?
--
Ticket URL: <https://code.djangoproject.com/ticket/27708#comment:6>
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.329e510c78912b4cd16eee50ca686251%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.