From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
---|---|
To: | pgadmin-hackers(at)postgresql(dot)org, Dave Page <dpage(at)postgresql(dot)org> |
Subject: | Patch for column properties |
Date: | 2007-03-01 23:32:04 |
Message-ID: | 45E76274.5010104@lelarge.info |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Hi,
When someone set a default value for a column and set NOT NULL at the
same time, the query could fail if the table already contains NULL
values for this column. This patch adds an UPDATE statement to put the
DEFAULT value in this column for all NULL values (but only when you SET
NULL and SET DEFAULT the column at the same time).
I've done this patch for a friend but I don't quite like this patch
because of its behaviour. It doesn't warn the user. I think it would be
better to show a dialog telling that an UPDATE statement will be
executed because otherwise the whole action could fail.
So here are some questions :
* do you think this patch is worth it ?
* do I need to show a confirmation dialog ?
* do I need to check first if there's NULL values on this column ?
Thanks.
Regards.
--
Guillaume.
<!-- http://abs.traduc.org/
http://lfs.traduc.org/
http://docs.postgresqlfr.org/ -->
Attachment | Content-Type | Size |
---|---|---|
updatenull.patch | text/x-patch | 905 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Hiroshi Saito | 2007-03-02 00:30:06 | Re: Lack in PostgreSql (8.2.x, 8.1.x, 8.0.x) and pgAdmin (1.6.x) updated builds (build service) |
Previous Message | svn | 2007-03-01 18:22:14 | SVN Commit by dpage: r5963 - in trunk/pgadmin3: . pgadmin/ctl pgadmin/dlg pgadmin/frm pgadmin/include/images pgadmin/include/schema pgadmin/include/utils pgadmin/schema pgadmin/utils |