"cnliou" <[EMAIL PROTECTED]> writes:
> (2) What is the correct syntax to set time zones having 30
> minutes offset UTC?
"SET TIME ZONE 8.5" works, as does "SET TIME ZONE INTERVAL '08:30';"
regards, tom lane
---(end of broadcast)---
¡° Include¡m"Tom Lane" <[EMAIL PROTECTED]>¡nwrote:
>> So, what is the official syntax?
>
>See the SET command's reference page. I believe you need
to quote
>anything that doesn't look like an identifier or number.
Thank you very much! You have clarified all my timestamp and
time zone questions
"cnliou" <[EMAIL PROTECTED]> writes:
> So, what is the official syntax?
See the SET command's reference page. I believe you need to quote
anything that doesn't look like an identifier or number.
regards, tom lane
---(end of broadcast)-
Thank you! Tom,
>The documentation does not actually say any such thing,
although its
>failure to clarify what it *is* saying isn't great. I have
reworded it
>as follows in CVS tip:
>
>: Table B-4 shows the time zone abbreviations recognized by
PostgreSQL in
>: date/time input values. PostgreS
"cnliou" <[EMAIL PROTECTED]> writes:
> The documentation (Appendix B.2. Date/Time Key Words) says
> that the following SQL's are legal, but actually they are
> not:
> SET TIME ZONE TO ''
The documentation does not actually say any such thing, although its
failure to clarify what it *is* saying i
Hi!
Seeing no comments on the same issue I raised in
pgsql-general list, I am posting it here.
The documentation (Appendix B.2. Date/Time Key Words) says
that the following SQL's are legal, but actually they are
not:
SET TIME ZONE TO ''
(examples:
SET TIMEZONE TO 'NZDT';
SET TIMEZONE TO 'EST';
