On Feb 8, 2005, at 20:43, Christopher Kings-Lynne wrote:
Yeah, this is on my personal "hope to do for 8.1" list. At least the
country/city part, haven't really thought about the other one.
One of the two forms already works...can't quite remember which...
I think this is perhaps what you were tryin
Yeah, this is on my personal "hope to do for 8.1" list. At least the
country/city part, haven't really thought about the other one.
One of the two forms already works...can't quite remember which...
---(end of broadcast)---
TIP 3: if posting/reading t
> Hi,
>
> Just a quick check that the extension to AT TIME ZONE to
> allow specifying intervals as well as country/city is on the
> list for 8.1.
>
> I believe it was a fairly simple thing to do now that we have
> our own time zone library...
Yeah, this is on my personal "hope to do for 8.1"
Hi,
Just a quick check that the extension to AT TIME ZONE to allow
specifying intervals as well as country/city is on the list for 8.1.
I believe it was a fairly simple thing to do now that we have our own
time zone library...
Chris
---(end of broadcast)
Added to TODO.
---
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > TODO entry?
>
> * Merge hardwired timezone names with the TZ database; allow either kind
> everywhere a TZ name is currently taken
> * all
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> I wonder instead if it will be possible to store a timestamp without
> timezone in one field, and a timezone in another field. So I can get
> back a timestamp at the second-field timezone.
"f1 AT TIME ZONE f2" would be exactly the way to do that.
> I
On Tue, Aug 24, 2004 at 03:16:30PM -0400, Shahbaz Javeed wrote:
People,
> I wonder whether this TODO item also covers cases such as inserting
> into a table where one field is time in the local timezone and the
> other is time in GMT. Not sure if such a thing is desirable or even
> possible (in
Folks,
I wonder whether this TODO item also covers cases such as inserting
into a table where one field is time in the local timezone and the
other is time in GMT. Not sure if such a thing is desirable or even
possible (in the SQL standard). The syntax I'm imagining feels pretty
awkward.
I gues
Bruce Momjian <[EMAIL PROTECTED]> writes:
> TODO entry?
* Merge hardwired timezone names with the TZ database; allow either kind
everywhere a TZ name is currently taken
* allow customization of the known set of TZ names (generalize the
present australian_timezones hack)
I'm not sure whether w
TODO entry?
---
Tom Lane wrote:
> Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
> > With the new timezone stuff, is there any reason this shouldn't be made
> > to work now in CVS:
> > test=# select current_timestamp a
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
> With the new timezone stuff, is there any reason this shouldn't be made
> to work now in CVS:
> test=# select current_timestamp at time zone 'Australia/Perth';
> ERROR: time zone "australia/perth" not recognized
Lack of round tuits. We have
With the new timezone stuff, is there any reason this shouldn't be made
to work now in CVS:
test=# select current_timestamp at time zone 'Australia/Perth';
ERROR: time zone "australia/perth" not recognized
Chris
---(end of broadcast)---
TIP 2: you
> template1=# select current_timestamp(0) at time zone 'Australia/Sydney';
> ERROR: Time zone 'australia/sydney' not recognized
The input is done using an internal lookup, not your system's time zone
database. Much faster; setting time zone variables for every input will
be substantially slower
What's with this?
template1=# select current_timestamp(0);
timestamptz
2002-08-21 16:39:40+08
(1 row)
template1=# set time zone 'Australia/Sydney';
SET
template1=# select current_timestamp(0);
timestamptz
2002-08-21 18:39:49+10
(1 r
14 matches
Mail list logo
