On Sat, Mar 5, 2011 at 1:29 PM, Karen Tracey <kmtra...@gmail.com> wrote: > On Fri, Mar 4, 2011 at 10:24 AM, Viktor Kojouharov <vkojouha...@gmail.com> > wrote: >> >> I'm testing my software with the new rc1 release of django 1.3, and I came >> onto a particularly nasty problem. >> I have a model which uses a Postgresql 'point' type, for which I've >> defined a field as: >> http://dpaste.com/472467/ >> >> I also have another model, which references this one with a foreign key. >> When saving an instance from this other model, django throws the following >> exception: >> http://dpaste.com/472475/ >> The exception is due to the new 'DISTINCT' part of the SELECT query. >> Because of the point field, there is no way to select 'unique' entries, >> because Postresql cannot compare points. >> So the question is, is there any way to turn off this distinct query, and >> just force django to assume that all entries are unique? > > Looks like the change that added distinct to this query is this one: > > http://code.djangoproject.com/changeset/15607 > > It's probably best if you open a ticket in trac > (http://code.djangoproject.com/newticket) for this. I can't think offhand > how to solve both the problem that changeset fixed and the one you are > encountering....
I can't see an obvious fix here either. Given the timeframe, we may need to roll back this fix, live with the older bug, and look at it again in the 1.4 timeframe. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
