#12400: column "X" named in key does not exist error when models.PointField
used in
unique_together
------------------------+------------------------------------
Reporter: monkut | Owner: claudep
Type: Bug | Status: new
Component: GIS | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------+------------------------------------
Comment (by claudep):
Does that mean that Oracle doesn't support unique indexes on geometry
fields? If that's the case, we'll probably need a new database feature.
Then the difficulty will be to conditionally create the index during
tests. As usual, I'm not able to work on Oracle fixes, but I'm available
to discuss/help.
More generally, being able to skip some model import or creation depending
on the backend would be useful for other tests too (gis, postgres, etc.).
--
Ticket URL: <https://code.djangoproject.com/ticket/12400#comment:13>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.a9a0f2e749b7fb47c4ff4d981f1aba49%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
