I opened the ticket: http://code.djangoproject.com/ticket/10182
Thanks. On Feb 3, 1:25 am, Russell Keith-Magee <freakboy3...@gmail.com> wrote: > On Mon, Feb 2, 2009 at 4:46 PM,omat<o...@gezgin.com> wrote: > > > I just remembered that the above error occured when running on > > Postgresql 8.2. Sorry for the misinformation about SQLite. > > > Then to give it a try with SQLite, I built a fresh database with > > syncdb on SQLite. > > > This time, at the same point, I get a: > > > OperationalError: no such column: tagging_taggeditem.added > > > This is very strange, because the column 'added' is surely there. > > I can now confirm I am seeing the same problem. It appears that the > table names aren't being correctly promoted in the GROUP BY clause for > the inner query. > > If you could open a ticket providing all the detail you have provided > here, I will ensure this bug gets fixed before we release v1.1 > > Many Thanks, > Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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 -~----------~----~----~----~------~----~------~--~---
