Skip site navigation (1) Skip section navigation (2)

Re: Inconsistent Errors on Row Comparisons

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
Cc: pgsql-hackers Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Inconsistent Errors on Row Comparisons
Date: 2009-06-30 18:46:12
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
"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

In response to


pgsql-hackers by date

Next:From: Tom LaneDate: 2009-06-30 18:48:26
Subject: Re: Inconsistent Errors on Row Comparisons
Previous:From: Josh BerkusDate: 2009-06-30 18:41:58
Subject: Re: 8.5 development schedule

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group