Nikhil Sontakke wrote:
Hi,
We've discussed before the idea that NOT NULL constraints should be
explicitly represented in pg_constraint, just like general CHECK
constraints (this would allow them to be named, have sane inheritance
behavior, etc). If we had that, then
Bruce Momjian br...@momjian.us writes:
Nikhil Sontakke wrote:
Warrants an entry in the TODO items list:
* make NOT NULL constraints have pg_constraint entries, just like CHECK
constraints
This is now a TODO item (I just updated the description):
Store the constraint names of NOT
Tom Lane wrote:
Bruce Momjian br...@momjian.us writes:
Nikhil Sontakke wrote:
Warrants an entry in the TODO items list:
* make NOT NULL constraints have pg_constraint entries, just like CHECK
constraints
This is now a TODO item (I just updated the description):
Store the
Hi,
We've discussed before the idea that NOT NULL constraints should be
explicitly represented in pg_constraint, just like general CHECK
constraints (this would allow them to be named, have sane inheritance
behavior, etc). If we had that, then pg_attribute.attnotnull could
indicate the OR
On Thu, Apr 2, 2009 at 3:25 AM, Jacky Leng lengjianq...@163.com wrote:
Considering the following sequence:
create table t(a int primary key);
alter table t drop constraint t_pkey;
insert into t values(null);
ERROR: null value in column a violates not-null constraint
My question
Hi,
Considering the following sequence:
create table t(a int primary key);
alter table t drop constraint t_pkey;
insert into t values(null);
ERROR: null value in column a violates not-null constraint
My question is, why null is not allowed to be inserted after primary
On Thu, Apr 2, 2009 at 8:24 AM, Nikhil Sontakke
nikhil.sonta...@enterprisedb.com wrote:
Hi,
Considering the following sequence:
create table t(a int primary key);
alter table t drop constraint t_pkey;
insert into t values(null);
ERROR: null value in column a violates
Hi,
Making a column into the primary key forces the column to NOT NULL.
You'll need to DROP NOT NULL separately.
It's probably possible to beat on the code hard enough to fix this,
Yeah it will be a matter of finding the affected column entries and
invoking
the removal of the not
Robert Haas robertmh...@gmail.com writes:
Actually it's more complicated than that. You'd need to remember
whether or not the NOT NULL was added when the primary key was added,
or whether it was there before, and only drop it if it wasn't there
before.
We've discussed before the idea that
