Horton
Menu

Re: operator exclusion constraints

Josh Berkus <josh@agliodbs.com>

View thread
From: Josh Berkus <josh@agliodbs.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Jeff Davis <pgsql@j-davis.com>, Tom Lane <tgl@sss.pgh.pa.us>, Peter Eisentraut <peter_e@gmx.net>, Simon Riggs <simon@2ndQuadrant.com>, pgsql-hackers@postgresql.org
Date: 2009-11-20T04:36:59Z
Lists: pgsql-hackers 
RObert,

> I guess I'm going to have to vote -1 on this proposal.  I code see
> inventing a pgsql-specific SQLSTATE value for exclusion constraints,
> since they will be a pgsql-specific extension, but reusing the unique
> key violation value seems misleading.  I admit it may help in a
> limited number of cases, but IMHO it's not worth the confusion.

I'd rather have a new one than just using "contstraint violation" which
is terribly non-specific, and generally makes the application developer
think that a value is too large.

--Josh BErkus