[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pgsql-hackers
Subject:    Re: [HACKERS] Re: [patch] Include detailed information about a
From:       "Kevin Grittner" <Kevin.Grittner () wicourts ! gov>
Date:       2011-11-29 20:24:40
Message-ID: 4ED4EB2802000025000435F2 () gw ! wicourts ! gov
[Download RAW message or body]

Tom Lane <tgl@sss.pgh.pa.us> wrote:
 
> I was wondering in particular whether it wouldn't be appropriate
> to include the same errdetail in ExecConstraints's other check,
> the one for null in not-null columns.  Arguably a not-null check
> is just a slightly optimized form of a CHECK constraint, and
> anyway if you think you need row identification info for a CHECK
> failure I don't see why you'd not want it for NOT NULL failure. 
> Comments?
 
Makes sense to me.
 
-Kevin

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
[prev in list] [next in list] [prev in thread] [next in thread]