Re: Inconsistent Errors on Row Comparisons
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: "David E. Wheeler" <david(at)kineticode(dot)com>
- Cc: pgsql-hackers Hackers <pgsql-hackers(at)postgresql(dot)org>
- Subject: Re: Inconsistent Errors on Row Comparisons
- Date: Tue, 30 Jun 2009 14:46:12 -0400
- Message-id: <23691.1246387572@sss.pgh.pa.us> <text/plain>
"David E. Wheeler" <david(at)kineticode(dot)com> writes:
> On Jun 30, 2009, at 11:18 AM, Tom Lane wrote:
>> What's the argument
>> for needing to handle this differently from DATATYPE_MISMATCH?
> For my results_eq() in pgTAP, it could output different diagnostics.
Well, that's not terribly compelling ;-). I wouldn't have any big
objection to splitting out ERRCODE_COLUMN_COUNT_MISMATCH as a separate
SQLSTATE for 8.5 and beyond, but I doubt we'd consider back-patching
such a change. It's not clear to me whether you need a solution that
works in back branches.
regards, tom lane
Home |
Main Index |
Thread Index