hmm..
the SQL shouldn't be that complex.. it's pretty standard
can you try running it without the date ?
or perhaps change

the with content_type_id in (30) to content_type_id = 30

On 19/07/2006, at 8:10 PM, tonemcd wrote:


Ian,
I think that's it - it definitely causes an SQL error on MySQL
4.1.18-standard.

Drat. Our main systems (where I intend to run django 'for real') are
stuck on the 4.1 series for the time being (hence why my machine is
still running 4.1.18-standard). However, as I make the final decisions
on what server versions we use, this could change ... ;)

Tone



--~--~---------~--~----~------------~-------~--~----~
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 [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---

Reply via email to