From: | "Dan Wilson" <phpPgAdmin(at)acucore(dot)com> |
---|---|
To: | <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Modifying NOT NULL Constraint |
Date: | 2000-06-14 03:25:18 |
Message-ID: | 005301bfd5b0$2b3de420$db7dfea9@dwilson |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
In the following archived email:
http://www.postgresql.org/mhonarc/pgsql-admin/2000-05/msg00025.html
this was posed as a solutions to modifying the NOT NULL constraint:
>update pg_attributes set attnotnull = 'f' where oid = oidofnotnullcolumn;
>vacuum analyze;
I didn't find any further comment on this so I decided to go right to the
source...
Is this recommended or not?
Are there any side effects of which I should be aware before attempting to
use this?
If this is not a valid way to accomplish the modification of the NOT NULL
constraint, then are there plans for an implementation of it (I enjoy the
new ALTER COLUMN DEFAULT)?
Thanks,
-Dan Wilson
phpPgAdmin Author
http://www.phpwizard.net/phpPgAdmin
Please reply to me directly as I'm not subscribed to the list.
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2000-06-14 03:26:36 | Re: setproctitle |
Previous Message | Bruce Momjian | 2000-06-14 03:19:19 | Re: Patch 0.2 for Re: [HACKERS] Caching number of blocks in relation to avoi lseek. |