On Fri, Sep 5, 2008 at 1:41 AM, Benedict Verheyen < [EMAIL PROTECTED]> wrote:
> > Because the datestyle in the sql statement is passes as Ymd, i tried to > set the datestyle in the postgres.conf file als datestyle = 'iso, ymd' and datestyle = 'sql, us' but they all resulted in the same error. Does postgres cache the settings into a database table? Is there some kind of flush command? I am surprised that this didn't work. This should have been the thing that you needed to do to fix it. Maybe there's a bug in postgres (seems unlikely), or you've done something wrong. I would still work on this front, because this fix is going to be far, far easier to implement and maintain than the alternatives. Is there anyway i can force Django to present dates to the database backend > as > dmY instead of Ymd. Setting DATE_FORMAT and DATETIME_FORMAT doesn't seem to > have an effect on this. > I suspect not, but you can dive into the django code to check. You might be able to hook into the database connection routines, and do a SET DATESTYLE on each connection. You probably can get away with doing this in your application code on each connection, and avoid making changes to the Django source; although you do have to then mind django's connection management a bit. It's not efficient, it's not the right way to do it, but for testing it could work. --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
