Re: date formatting and tab-complete patch

From: Manuel Sugawara <masm(at)fciencias(dot)unam(dot)mx>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Karel Zak <zakkr(at)zf(dot)jcu(dot)cz>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL Hackers Mailing List <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: date formatting and tab-complete patch
Date: 2002-03-07 17:30:47
Message-ID: m3vgc8ffp4.fsf@dep4.fciencias.unam.mx
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:

> OK, I have read this thread and am unsure how to proceed. Is this
> something to apply or does it require more work. The full thread is
> at:

The problem is that we did not reach any agreement :-(. What I would
like, personally, is make the present more locale aware, so we can
reuse code already done with minimal impact (think nls). However Karel
insists that

select to_char(cast('2001/01/01' as timestamp),'fmDDMonYYYY');

should always lead to '1Jan2001' no matter which localization is in
use and I didn't understand the reasons for this. Any way is easy to
implement, however I would like to see agreement on which is the best
way to go.

> I will apply the tab completion fix. That is a separate issue.

When you are there, can you fix the `full' part of the vacuum that
does not complete?

Regards,
Manuel.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Manuel Sugawara 2002-03-07 17:34:28 Re: date formatting and tab-complete patch
Previous Message Tom Lane 2002-03-07 16:55:48 Re: Small fix for _equalValue()

Browse pgsql-patches by date

  From Date Subject
Next Message Manuel Sugawara 2002-03-07 17:34:28 Re: date formatting and tab-complete patch
Previous Message Fernando Nasser 2002-03-07 16:57:34 Reorder definitions in parsenodes.h