Re: Timestamp Conversion Woes Redux
От | Dave Cramer |
---|---|
Тема | Re: Timestamp Conversion Woes Redux |
Дата | |
Msg-id | A3CA1F32-2150-4F77-A691-7E39B392265C@fastcrypt.com обсуждение исходный текст |
Ответ на | Re: Timestamp Conversion Woes Redux (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-jdbc |
On 22-Jul-05, at 9:42 AM, Tom Lane wrote: > Dave Cramer <pg@fastcrypt.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 > >
В списке pgsql-jdbc по дате отправления: