Re: Incomplete compatibility information for triggers
От | Josh Kupershmidt |
---|---|
Тема | Re: Incomplete compatibility information for triggers |
Дата | |
Msg-id | CAK3UJRGSqgac5wvhJgs4vVU8M2C1=nKj3BciTquO2Nbx23a+NQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Incomplete compatibility information for triggers (Louis-Claude Canon <louis-claude.canon@femto-st.fr>) |
Ответы |
Re: Incomplete compatibility information for triggers
|
Список | pgsql-docs |
On Sun, Nov 11, 2012 at 3:52 PM, Louis-Claude Canon <louis-claude.canon@femto-st.fr> wrote: > the compatibility section of the "create trigger" page > (http://www.postgresql.org/docs/devel/static/sql-createtrigger.html) claims > that a missing functionality is the ability to define aliases for the "old" > and "new" rows or tables. If I am understanding this correctly, another > related missing functionality is that PostgreSQL does not allow the old and > new tables to be referenced for statement-level triggers (i.e., the "OLD > TABLE" that contains all the deleted/modified rows in case of > deletion/update). I think this is also worth noting as any workaround for it > seems to be more difficult (if possible at all) than for the missing alias > feature. +1, it seems like a useful missing piece from the SQL:2011 standard. Care to send a documentation patch? Josh
В списке pgsql-docs по дате отправления: