Skip site navigation (1) Skip section navigation (2)

Re: Timestamp Conversion Woes Redux

From: Dave Cramer <pg(at)fastcrypt(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Oliver Jowett <oliver(at)opencloud(dot)com>,Kris Jurka <books(at)ejurka(dot)com>,Christian Cryder <c(dot)s(dot)cryder(at)gmail(dot)com>, pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Timestamp Conversion Woes Redux
Date: 2005-07-22 14:13:16
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-jdbc
On 22-Jul-05, at 9:42 AM, Tom Lane wrote:

> Dave Cramer <pg(at)fastcrypt(dot)com> writes:
>> One issue I have is that the server returns some time zones in
>> lowercase.
>> ie EST -> est
>>      EST5EDT -> est5edt
> I think that in some contexts the case you will get back is what you
> give in the SET command.  So do
>     set timezone = 'EST5EDT';
> not
>     set timezone = EST5EDT;
> (the latter is downcased as if it were an identifier).
Ick .... this makes things tougher ... The user won't necessarily  
quote it if they change it.

I guess if we restrict changing it, as per your other suggestion,  
then this goes away.
>             regards, tom lane
> ---------------------------(end of  
> broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
>        choose an index scan if your joining column's datatypes do not
>        match

In response to

pgsql-jdbc by date

Next:From: Kevin GrittnerDate: 2005-07-22 16:30:12
Subject: Re: Timestamp Conversion Woes Redux
Previous:From: Marc HerbertDate: 2005-07-22 13:56:40
Subject: getObject(<oid>) returns integer instead of LargeObject handle ?

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group