#12400: column "X" named in key does not exist error when models.PointField used in unique_together ------------------------+--------------------------------------------- Reporter: monkut | Owner: claudep Type: Bug | Status: closed Component: GIS | Version: master Severity: Normal | Resolution: fixed Keywords: | Triage Stage: Ready for checkin Has patch: 1 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 ------------------------+--------------------------------------------- Changes (by Claude Paroz <claude@…>):
* status: assigned => closed * resolution: => fixed Comment: In [changeset:"01ec127baec38b7f8281e6eca9def40f22c9e5ad" 01ec127b]: {{{ #!CommitTicketReference repository="" revision="01ec127baec38b7f8281e6eca9def40f22c9e5ad" Fixed #12400 -- Allowed geometry fields in unique_together Thanks Tim Graham for the review. }}} -- Ticket URL: <https://code.djangoproject.com/ticket/12400#comment:11> 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.2cb8a192e21936efceb6945ff252ce8e%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.