Re: ERROR: check constraint - PostgreSQL 9.2

Hello

Althought both options are technically correct, I guess that the first one is the only reasonable one. What is the point of having a
check constraint that is not checked? If all fields in the check constraint must not be null there must be a reason for it. Possibly
the "wrong" data is useless anyway (some test data that was not deleted) or the constraint only applies from a certain point in time
because something in the system built on top of it changed. In the latter case, since the data has a time stamp you may extend the
constraints to include the point in time from which it must apply.

Bye
Charles

> -----Original Message-----
> From: pgsql-general-owner(at)postgresql(dot)org [mailto:pgsql-general-owner(at)postgresql(dot)org] On Behalf Of Christophe Pettus
> Sent: Montag, 25. Januar 2016 05:18
> To: Postgres General <pgsql-general(at)postgresql(dot)org>
> Subject: Re: [GENERAL] ERROR: check constraint - PostgreSQL 9.2
>
>
> On Jan 24, 2016, at 8:12 PM, "drum(dot)lucas(at)gmail(dot)com" <drum(dot)lucas(at)gmail(dot)com> wrote:
>
> > How can I solve the problem? How can I get the command successfully be done?
>
> Two options:
>
> 1. Fix the data.
>
> 2. Use the NOT VALID option on ALTER TABLE ... ADD constraint, which allows the addition of a constraint without
> actually checking its validity.
>
> --
> -- Christophe Pettus
> xof(at)thebuild(dot)com
>
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general