> If you don't want to use a custom version of Django, and can't wait
> for 1.4, you should be able to set the time zone for per database
> user. Connect to the database with your database user, and do this:
> ALTER USER "thedbuser" SET TIME ZONE 'wanted_zone'; -- where
> wanted_zone would be UTC f
On Jan 30, 11:21 am, Ashe wrote:
> Hello,
>
> I have been using django 1.3.1 for some months.
> I had a long time bug and I finally took some hours to track it.
> Sometimes in my admin interface (not the default django one), all the
> query based on datetime object have a very strange behavior.
>
On Jan 30, 4:54 am, Ramiro Morales wrote:
> On Mon, Jan 30, 2012 at 6:21 AM, Ashe wrote:
> > Could you help me make this modification working in the 1.3.1 ? I
> > looked at the file modified in the changeset 17128, but it looks like
> > it changed a lot between the release and this changeset.
>
On Mon, Jan 30, 2012 at 6:21 AM, Ashe wrote:
> Could you help me make this modification working in the 1.3.1 ? I
> looked at the file modified in the changeset 17128, but it looks like
> it changed a lot between the release and this changeset.
Are you sure?. I've just tried and this is what I've
Hello,
I have been using django 1.3.1 for some months.
I had a long time bug and I finally took some hours to track it.
Sometimes in my admin interface (not the default django one), all the
query based on datetime object have a very strange behavior.
After some research, I ended up with the conclu
5 matches
Mail list logo
