Re: [BUGS] BUG #2221: Bad delimiters allowed in COPY ...

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: David Fetter <david(at)fetter(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net>, neilc(at)samurai(dot)com, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: [BUGS] BUG #2221: Bad delimiters allowed in COPY ...
Date: 2006-02-01 06:16:08
Message-ID: 26453.1138774568@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-patches

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Attached is a patch that errors for \r and \n in delimiter and null. I
> kept the ERRCODE_FEATURE_NOT_SUPPORTED error code because that is what
> all the other error tests use in the copy code in that area.

I'd go with INVALID_PARAMETER_VALUE, I think. ISTM that
FEATURE_NOT_SUPPORTED is appropriate for places where we might someday
support the case the error is rejecting. For instance the error just
above your patch is for a multi-character delimiter string. That isn't
completely senseless, it's just not implemented. But we're not ever
going to allow a delimiter setting that conflicts with end-of-line,
and I don't foresee allowing some other value for end-of-line ;-)
... so this check isn't going to be removed someday.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message David Fetter 2006-02-01 06:56:05 Re: [BUGS] BUG #2221: Bad delimiters allowed in COPY ...
Previous Message Bruce Momjian 2006-02-01 04:33:26 Re: [BUGS] BUG #2221: Bad delimiters allowed in COPY ...

Browse pgsql-patches by date

  From Date Subject
Next Message David Fetter 2006-02-01 06:56:05 Re: [BUGS] BUG #2221: Bad delimiters allowed in COPY ...
Previous Message Bruce Momjian 2006-02-01 04:33:26 Re: [BUGS] BUG #2221: Bad delimiters allowed in COPY ...