Re: In RULEs, INSERT does not use DEFAULTs
От | Tom Lane |
---|---|
Тема | Re: In RULEs, INSERT does not use DEFAULTs |
Дата | |
Msg-id | 10814.1118634509@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: In RULEs, INSERT does not use DEFAULTs (David Fetter <david@fetter.org>) |
Ответы |
Re: In RULEs, INSERT does not use DEFAULTs
Re: In RULEs, INSERT does not use DEFAULTs |
Список | pgsql-hackers |
David Fetter <david@fetter.org> writes: > I believe this isn't just my problem. Without access to a the > underlying column's DEFAULT, how can people implement the automated > WRITEable VIEWs? That's a reasonable question, but translating "insert null" to "insert the default" is not a reasonable answer. There was some speculation just a couple days ago about inventing a function that would compute the default associated with some other table's column, but it's not clear how to make that work (in particular, how to declare the result type of such a function). Another possibility is a command along the lines ofALTER view ALTER col LINK DEFAULT TO othertable.col; (syntax open to argument of course) which accomplishes the same thing without having to figure a way to avoid the constraints of a specific function result type. regards, tom lane
В списке pgsql-hackers по дате отправления: