Hi, Robert Haas <robertmh...@gmail.com> writes: > Maybe we should try to split the baby here and defer the question of > whether to expose any of the parse tree internals, and if so how much, > to a future release. It seems to me that we could design a fairly > useful set of functionality around AFTER-CREATE, BEFORE-DROP, and > maybe even AFTER-ALTER triggers without exposing any parse tree > details.
+1 Also remember that you have a “normalized” command string to play with. Lots of use cases are already ok here. The other ones would need a tree representation that's easy to consume, which in the current state of affairs (I saw no progress on the JSON data type and facilities) is very hard to imagine when you consider PLpgSQL. So unless I hear about a show stopper, I'm going to work some more on the command trigger patch where I still had some rough edges to polish. Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
