Justin Deoliveira ha scritto:
>> Is there any reason why you forced GMT timezone for
>> dates? I think 2007-07-04+02:00 or simply 2007-07-04
>> would be both more correct.
> I don't think this is something that is done explicitly... i think its
> just the behaviour of the encoder.
Hmm someth
As quoted from Andrea Aime <[EMAIL PROTECTED]>:
> only on 1.6.x,
No problem for me, I can easily upgrade to 1.6. I saw that some of the
other issues that had a Fix-for 1.5.2 have also been set to 1.6, which
is fine by me.
> when I come back from vacation
Have fun!
Regards,
--
-- Gertjan van O
Gertjan van Oosten ha scritto:
>>> 2007-07-03+00:00
>
> However, this is clearly wrong, as can be seen when you take this field
> in a round-trip from and to the database: if you store it again, it will
> probably show up in the database as 2007-07-03. So regardless of the
> stance you take on *
As quoted from Justin Deoliveira <[EMAIL PROTECTED]>:
> Andrea Aime wrote:
> > Now, with the following data in the db:
> > dt| timetest | datetest
> > -+--+
> > 2007-07-02 12:06:37.671 | 15:48:50.531 | 2007-07-04
> >
> Hmmm
Andrea Aime wrote:
> Hi,
> I'm doing some tests on postgis and I have some timezone issues.
> I live in Italy, some I'm +2 compared to Greenwich.
>
> Now, with the following data in the db:
> dt| timetest | datetest
> -+--+
Hi,
I'm doing some tests on postgis and I have some timezone issues.
I live in Italy, some I'm +2 compared to Greenwich.
Now, with the following data in the db:
dt| timetest | datetest
-+--+
2007-07-02 12:06:37.671 | 15:
