From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Gavin Sherry <swm(at)linuxworld(dot)com(dot)au>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [PATCHES] WITH DELIMITERS in COPY |
Date: | 2002-04-15 03:19:51 |
Message-ID: | 6368.1018840791@sss.pgh.pa.us |
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:
> Gavin Sherry wrote:
>> CREATE DATABASE also fills out a list in the same fashion =). I will
>> however have a look at revising this patch to use DefElem later today.
> Oh, I see that now. Which method do people prefer. We should probably
> make them all use the same mechanism.
Consistency? Who needs consistency ;-) ?
Seriously, I do not see a need to change either of these approaches
just for the sake of changing it. CREATE DATABASE is okay as-is, and
so are the statements that use DefElem. I tend to like DefElem better
for the statements that we change around frequently ... for instance
the recent changes to the set of volatility keywords for functions
didn't require any changes to the grammar or the parsenode definitions.
But I think that a simple struct definition is easier to understand,
so I favor that for stable feature sets.
As for which one is better suited for COPY, I don't have a strong
opinion, but lean to DefElem. Seems like COPY will probably keep
accreting new features.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2002-04-15 03:21:54 | Re: ANSI Compliant Inserts |
Previous Message | Tom Lane | 2002-04-15 03:09:09 | Re: ANSI Compliant Inserts |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2002-04-15 03:21:54 | Re: ANSI Compliant Inserts |
Previous Message | Tom Lane | 2002-04-15 03:09:09 | Re: ANSI Compliant Inserts |