From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "James Newman" <jamesn(at)cisonic(dot)com>, <pgadmin-support(at)postgresql(dot)org> |
Subject: | Re: restrict null in column?? |
Date: | 2002-05-09 07:54:48 |
Message-ID: | 214E9C0A75426D47A876A2FD8A07426E66A0@salem.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
-----Original Message-----
From: James Newman [mailto:jamesn(at)cisonic(dot)com]
Sent: 08 May 2002 20:55
To: pgadmin-support(at)postgresql(dot)org
Subject: [pgadmin-support] restrict null in column??
Hi,
I'm trying to design a database and am trying to restrict the
use of null values in the columns. When I create the column and check
the box to restrict the null values, I can't save it. It gives me this
error:
-2147467259: error while executing the query;
ERROR: adding not null columns is not implemented. Add the
column, then use Alter Table Add Constraint.
Sorry, that's a bug in pgAdmin, it shouldn't let you even select it.
In pgAdmin, you can view the column properties after you saved
it, but can't change the null value state. Am I doing something wrong?
do I have an old version or is this just another Postgres issue that I
have to work around?
This is just another PostgreSQL issue that I believe has been fixed for
7.3 (and which pgAdmin will support of course). In the meantime, (at
completely your own risk, having take backups etc) you could alter the
relevant attribute in the pg_class attribute and then restart the
postmaster. Or dump to text file, modify the table definition and then
reload.
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | Sunrise(Yangon) | 2002-05-14 04:41:54 | sunrise : plpgsql language error |
Previous Message | Dave Page | 2002-05-09 07:47:23 | Re: Database Migration Plugin and auto increments |