> It may indeed be that the MAX clause is using "mat_foo" instead of the > assigned correlation U0. What happens if you paste the two SQLs into a > query window in PgAdmin 3 and execute them. If the 1.2 query fails > with the same error message, I'd report a bug. > > If it doesn't fail, it's still a Django issue, but I have no idea what > it could be. I'm very new to Django; not new to databases.
Ah, I forgot to mention: it does fail when copy/pasting the query django 1.2 generated in psql/pgadmin. I'm not very familiar with postgres and complex queries like this (and I suspect there is a better way of doing what I'm doing) ; it's obvious the difference between the 2 queries is what's causing my problem, but I have no idea *why*, therefore I haven't reported the bug yet. An explanation from a django wizard or a psql ninja would be great :-) -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
