> You could possibly make it work if you were willing to include the word > TYPE when trying to respecify column type: > > ALTER TABLE blah ALTER [COLUMN] col [TYPE int4] [NOT NULL] [DEFAULT 32]; > > Also I agree with Fernando that trying to make the word COLUMN optional > is likely to lead to conflicts.
But all the other ALTER TABLE/Alter Column commands have it optional... I have throught of at least two problems with changing nullability. The first is primary keys. I have to prevent people setting a column involved in a PK to null, right? The second is DOMAINs - what if they change a NOT NULL domain in a colun to NULL? Shoudl I just outright prevent people from altering domain-based columns nullability> Chris ---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
