On Tue, Nov 06, 2007 at 10:00:43AM -0500, Tom Lane wrote:
> Heikki Linnakangas <heikki(at)enterprisedb(dot)com> writes:
> > Not sure that's enough of a use case to justify not banning it...
>
> Yeah, it probably is.
It's reasonably easy to do this instead:
CREATE TABLE foo (
one INTEGER NOT NULL UNIQUE CHECK (one = 1)
);
The bug (for me) was that it's possible to get the database into an
inconsisant state, with no warning or obvious way to back out.
Sam