Re: NOT NULL constraint & value too large during import

From: astalavista <nobody_at_nowhere.com>
Date: Wed, 29 Mar 2006 21:43:00 +0200
Message-ID: <442ae340$0$14294$626a54ce@news.free.fr>

> An initial 'alter constraint <constraint name> enable novalidate;' will
> enable the constraint, list it as valid, yet not check existing values
> in the table, some of which could be NULL. This is true even for a
> primary key constraint:

I thought the validated status means
all old data checked the constraints
I was wrong ?

>
> A NOT NULL column contains NULL values, due to the novalidate directive
> when the constraint was created. No others may be added, but the
> existing values remain.
> That isn't possible, as the values being passed to the load operation
> are 4 characters in length:
>
> I would check your original definition again.
It is an export/import the definition is the same in the two databases , no ? Received on Wed Mar 29 2006 - 13:43:00 CST