Re: BUG #2974: broken CHECK constraint with varchar

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Michal Schwarz <misch(at)czechin(dot)cz>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #2974: broken CHECK constraint with varchar
Date: 2007-02-08 16:56:50
Message-ID: 200702081656.l18Guo218701@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Michal Schwarz wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2974
> Logged by: Michal Schwarz
> Email address: misch(at)czechin(dot)cz
> PostgreSQL version: 8.1.7
> Operating system: Fedora Core 6
> Description: broken CHECK constraint with varchar
> Details:
>
> CREATE TABLE t (c VARCHAR(20));
> ALTER TABLE t ADD CONSTRAINT xyz CHECK (c IN ('A','B','C'));
> INSERT INTO t VALUES ('A');
>
> Results:
> ERROR: attribute 1 has wrong type
> DETAIL: Table has type character varying, but query expects character
> varying.
>
> In previous versions, everything worked correctly. Problem arised in 8.1.7
> (maybe only in Fedora release???). When i returned back to 8.1.6, everything
> worked again.

Please upgrade to 8.1.8. That was a rush release to fix this bug added
in 8.1.7.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Bruce Momjian 2007-02-08 16:57:19 Re: BUG #2975: UNIQUE INDEX doesn't work
Previous Message Tom Lane 2007-02-08 16:55:04 Re: Possible problem with type bigserial in pg_dump/pg_restore