Re: SET NULL / SET NOT NULL
От | Tom Lane |
---|---|
Тема | Re: SET NULL / SET NOT NULL |
Дата | |
Msg-id | 29097.1016776370@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: SET NULL / SET NOT NULL ("Christopher Kings-Lynne" <chriskl@familyhealth.com.au>) |
Ответы |
Re: SET NULL / SET NOT NULL
Re: SET NULL / SET NOT NULL |
Список | pgsql-hackers |
"Christopher Kings-Lynne" <chriskl@familyhealth.com.au> writes: > Say in the future we want to support changing column type as well. How > would we work that in? > ALTER TABLE blah ALTER COLUMN col SET int4; ?????? Seems one keyword shy of a load; I'd prefer ALTER TABLE blah ALTER COLUMN col SET TYPE int4; Otherwise, every keyword that might appear after SET will have to be fully reserved (else it couldn't be distinguished from a type name). I like the "SET NULL"/"SET NOT NULL" variant better than SET/DROP, even though "SET NULL" is perhaps open to misinterpretation. "DROP NOT NULL" seems just as confusing for anyone who's not read the documentation :-( regards, tom lane
В списке pgsql-hackers по дате отправления: