On 6/12/06, Matt McClure <[EMAIL PROTECTED]> wrote: > > I received in a private email: > > Hello Matthew, > > > > I'm seeing the exact same "date_hierarchy" problem and was wondering > > if you received a solution offline and/or figured it out. > > > > Seems like the problem is somewhere among my Python 2.3.3, MySQLdb > > 1.2.1 and the MySQL 3.23.53, 'cause I've got a Python 2.4.3, MySQLdb > > 1.2.1 and MySQL 4.0.26-standard setup where the "date_hierarchy" in > > models.py works just fine. > > > > Regards, John Eugene, Ore. > > I haven't found an answer to my question. > > FWIW, here are my versions: > > [EMAIL PROTECTED] ~]$ rpm -qf > /usr/lib/python2.3/site-packages/MySQLdb/sets.py > MySQL-python-0.9.2-4 > [EMAIL PROTECTED] ~]$ rpm -q python > python-2.3.4-13.1 > [EMAIL PROTECTED] ~]$ rpm -q mysql > mysql-3.23.58-16.FC3.1 > > If I had to take a guess, I'd say that MySQL was probably changed > between 3.23 and 4.0.26 to accept the syntax Django is using. But > that's only a naive guess.
Your original error was: "You have an error in your SQL syntax near '(DATE_FORMAT(`polls_poll`.`pub_date`, '%Y-01-01 00:00:00') AS DATETIME) FROM `p' at line 1" I'm going to guess that the bit before the leading parenthesis is "CAST", and CAST() does not exist prior to MySQL-4.0. http://dev.mysql.com/doc/refman/4.1/en/cast-functions.html Solution: I recommend MySQL-4.1 or newer with MySQL-python-1.2.1. -- The Pythonic Principle: Python works the way it does because if it didn't, it wouldn't be Python. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
