Richard Broersma Jr <[EMAIL PROTECTED]> writes:
> It seems that 'infinity' still can't be casted to a date. :-(
It's still on the TODO list.
regards, tom lane
---(end of broadcast)---
TIP 3: Have you checked our extensive FA
On Aug 13, 2007, at 0:35 , Naz Gassiep wrote:
As clearly stated in the documentation
http://www.postgresql.org/docs/8.2/interactive/datatype-
datetime.html#DATATYPE-TIMEZONES
Perhaps I'm thick, but I don't find that particular page to be
clear on this at all.
Had you read the document
Paul Lambert wrote:
Refer to this paragraph: (8.5.1.2)
For timestamp with time zone, the internally stored value is always in
UTC (Universal Coordinated Time, traditionally known as Greenwich Mean
Time, GMT). An input value that has an explicit time zone specified is
converted to UTC using th
Naz Gassiep wrote:
As clearly stated in the documentation
http://www.postgresql.org/docs/8.2/interactive/datatype-datetime.html#DATATYPE-TIMEZONES
Perhaps I'm thick, but I don't find that particular page to be clear on
this at all.
- Naz.
---(end of broadcast)---
As clearly stated in the documentation
http://www.postgresql.org/docs/8.2/interactive/datatype-datetime.html#DATATYPE-TIMEZONES
Perhaps I'm thick, but I don't find that particular page to be clear on
this at all.
- Naz.
---(end of broadcast)---
On Mon, Aug 13, 2007 at 02:47:06PM +1000, Naz Gassiep wrote:
> When entering data into a timestamptz field, if no timezone is added
> does it assume you've entered a UTC time, or the time at the timezone
> set in the session with SET TIMEZONE, or the local system time ?
i dont understand - why d
On Aug 12, 2007, at 23:47 , Naz Gassiep wrote:
When entering data into a timestamptz field, if no timezone is
added does it assume you've entered a UTC time, or the time at the
timezone set in the session with SET TIMEZONE, or the local system
time ?
As clearly stated in the documentati
