On Mon, Jun 30, 2008 at 4:29 AM, Antti Haapala <[EMAIL PROTECTED]> wrote:
>
> 2008/6/27 Tom Tobin <[EMAIL PROTECTED]>:
>>
>> Well, it stores the *offset*, which is virtually useless in real-world
>> applications.
>
> I haven't tested on 8.3, but on 8.2 it does not. In PostgreSQL, the datatype
> "t
2008/6/27 Tom Tobin <[EMAIL PROTECTED]>:
> On Fri, Jun 27, 2008 at 5:55 AM, Antti Haapala <[EMAIL PROTECTED]>
> wrote:
> >
> >
> > On 25 kesä, 19:12, "Tom Tobin" <[EMAIL PROTECTED]> wrote:
>
> Well, it stores the *offset*, which is virtually useless in real-world
> applications.
I haven't tested
On Fri, Jun 27, 2008 at 5:55 AM, Antti Haapala <[EMAIL PROTECTED]> wrote:
>
>
> On 25 kesä, 19:12, "Tom Tobin" <[EMAIL PROTECTED]> wrote:
>
>> All PostgresSQL supports in terms of *storage* is
>> a fixedtimezoneoffset, not the actual zoneinfo name; this isn't
>> very useful, and causes problems suc
On 25 kesä, 19:12, "Tom Tobin" <[EMAIL PROTECTED]> wrote:
> All PostgresSQL supports in terms of *storage* is
> a fixedtimezoneoffset, not the actual zoneinfo name; this isn't
> very useful, and causes problems such as the above.
Actually, in PostgreSQL TIMESTAMP WITH TIME ZONE does NOT store t
On Wed, Jun 25, 2008 at 11:17 AM, Ramiro Morales <[EMAIL PROTECTED]> wrote:
>
> On Wed, Jun 25, 2008 at 1:12 PM, Tom Tobin <[EMAIL PROTECTED]> wrote:
>
>>
>> I propose that the PostgresSQL backends start acting like the other
>> backends regarding time zones: they should start ignoring them
>> com
On Wed, Jun 25, 2008 at 1:12 PM, Tom Tobin <[EMAIL PROTECTED]> wrote:
>
> I propose that the PostgresSQL backends start acting like the other
> backends regarding time zones: they should start ignoring them
> completely (i.e., use a plain TIMESTAMP [WITHOUT TIME ZONE], and stop
> using SET TIME Z
Thanks to some happy signal magic, I've come up with a
"DateTimeZoneField" that takes a "time_zone" argument; time_zone can
be a tzinfo instance or a field lookup to a zoneinfo string (e.g.,
"America/Chicago"). The field can then consume any sort of datetime
object, and will always spit back a ti