Re: Timezone abbreviations - out but not in?

From: "Dave Page" <dpage(at)pgadmin(dot)org>
To: "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Timezone abbreviations - out but not in?
Date: 2008-06-10 15:59:50
Message-ID: 937d27e10806100859j79742638ra74475325a960b95@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jun 10, 2008 at 4:51 PM, Alvaro Herrera
<alvherre(at)commandprompt(dot)com> wrote:
> Dave Page wrote:
>> Right, but shouldn't we always output something we know we can read
>> back in (unambiguously), assuming a server with no user defined
>> abbreviations?
>
> That makes no sense because it amounts to saying that we can't ever use
> any abbreviation.

For user defined abbreviations, used for output, yes. But as Tom
points out, the user can remove or change abbreviations that way as
well so it wouldn't work then anyway.

> A more useful restriction would be to only output
> those that are in the set of input-acceptable abbreviations, but perhaps
> this is not easy to implement.

Or just output offsets in every case :-p

--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2008-06-10 16:01:05 Re: Core team statement on replication in PostgreSQL
Previous Message Alvaro Herrera 2008-06-10 15:51:52 Re: Timezone abbreviations - out but not in?