On Sat, Sep 16, 2006 at 04:19:48PM -0400, Tom Lane wrote:
> "Magnus Hagander" <[EMAIL PROTECTED]> writes:
> > Here goes. Tested only on win32 so far, but works there. No docs yet
> > either - need to know if it goes in first ;)
> I've applied this along with some extra work to get it to show GMT
>
On 2006-09-17, Tom Lane <[EMAIL PROTECTED]> wrote:
> "Magnus Hagander" <[EMAIL PROTECTED]> writes:
>>> Any view over the full timezone names should also include the
>>> corresponding data from zone.tab in the timezone library source.
>
>> Just noticed this mail, so that's not included in my patch.
On Sat, Sep 16, 2006 at 04:19:48PM -0400, Tom Lane wrote:
> I've applied this along with some extra work to get it to show GMT
> offsets and DST status, which should be useful for helping people
> to choose which setting they want. This effectively obsoletes
> Table B-5 as well as B-4 in the SGML
"Magnus Hagander" <[EMAIL PROTECTED]> writes:
>> Any view over the full timezone names should also include the
>> corresponding data from zone.tab in the timezone library source.
> Just noticed this mail, so that's not included in my patch.
BTW, now that the view is in, I can't help noticing that
"Magnus Hagander" <[EMAIL PROTECTED]> writes:
>>> Assuming we can sneak this in even though it's feature-freeze,
>>> want me to look for it?
>> Yeah, please take a look --- seeing the size of the code will
>> probably help us decide if it's too late for 8.2 or not.
> Here goes. Tested only on win
Gavin Sherry <[EMAIL PROTECTED]> writes:
> On Wed, 6 Sep 2006, Tom Lane wrote:
>> It's somewhat urgent to address this now, because pg_timezonenames is
>> sitting on the obvious name for such a view, and once we release 8.2
>> we won't be able to change it. On reflection I think the existing view
> >> In the CVS version there is a table with this information:
> >> http://developer.postgresql.org/pgdocs/postgres/view-pg-
> timezonenames
> >> .html
> >
> > Actually, what that view gives you is timezone offset
> abbreviations,
> > not the full zone names that you could use with SET TIME ZONE.
On Wed, 6 Sep 2006, Tom Lane wrote:
> Martijn van Oosterhout writes:
> > In the CVS version there is a table with this information:
> > http://developer.postgresql.org/pgdocs/postgres/view-pg-timezonenames.html
>
> Actually, what that view gives you is timezone offset abbreviations, not
> the ful
On 2006-09-06, Tom Lane <[EMAIL PROTECTED]> wrote:
> Martijn van Oosterhout writes:
>> In the CVS version there is a table with this information:
>> http://developer.postgresql.org/pgdocs/postgres/view-pg-timezonenames.html
>
> Actually, what that view gives you is timezone offset abbreviations, n
"Magnus Hagander" <[EMAIL PROTECTED]> writes:
> Assuming we can sneak this in even though it's feature-freeze, want me
> to look for it?
Yeah, please take a look --- seeing the size of the code will probably
help us decide if it's too late for 8.2 or not.
regards, tom lan
On Thu, Sep 07, 2006 at 05:29:04AM +1000, Naz Gassiep wrote:
> I am also rather baffled at the way "SAT" is changed from being
> interpreted as a day of the week in one mode, and a timezone in another.
Ugh. It'd be an argument if people actually used SAT as a timezone.
They don't, it's ACST.
Ha
> > In the CVS version there is a table with this information:
> >
> http://developer.postgresql.org/pgdocs/postgres/view-pg-timezonenames.
> > html
>
> Actually, what that view gives you is timezone offset
> abbreviations, not the full zone names that you could use
> with SET TIME ZONE. It st
I don't know about anyone else, but the whole australian_timezones thing
seems like an ugly hackaround to me.
You really shouldn't be pontificating about this if you haven't been
paying attention to recent development work ;-)
regards, tom lane
Aah, sorry, I don
Naz Gassiep <[EMAIL PROTECTED]> writes:
> I don't know about anyone else, but the whole australian_timezones thing
> seems like an ugly hackaround to me.
You really shouldn't be pontificating about this if you haven't been
paying attention to recent development work ;-)
r
Actually, what that view gives you is timezone offset abbreviations, not
the full zone names that you could use with SET TIME ZONE. It strikes
me that we should have a view for that as well. We could use code
similar to scan_available_timezones() to generate the view output.
It's somewhat urg
Martijn van Oosterhout writes:
> In the CVS version there is a table with this information:
> http://developer.postgresql.org/pgdocs/postgres/view-pg-timezonenames.html
Actually, what that view gives you is timezone offset abbreviations, not
the full zone names that you could use with SET TIME ZO
Naz Gassiep <[EMAIL PROTECTED]> writes:
> Martijn van Oosterhout wrote:
>> Err, where does postgres use this information? I beleive there is a
>> project on pgfoundary that has some standard datasets.
>>
> Currently, it is stored in /src/timezone/data/iso3166.tab and I propose
> to have it availa
Martijn van Oosterhout wrote:
In the CVS version there is a table with this information:
http://developer.postgresql.org/pgdocs/postgres/view-pg-timezonenames.html
Great, thanks for that
Err, where does postgres use this information? I beleive there is a
project on pgfoundary that has som
On Thu, Sep 07, 2006 at 04:07:58AM +1000, Naz Gassiep wrote:
> Any chance for a DB Client accessible list of allowable time zones? I've
> been told that the only way to get at this list is by looking through
> the source and lifting the list from zone.tab.
In the CVS version there is a table wit
Any chance for a DB Client accessible list of allowable time zones? I've
been told that the only way to get at this list is by looking through
the source and lifting the list from zone.tab.
While I'm at it, how about an accessible list of country codes? I know
that it's not core db functionali
20 matches
Mail list logo