Dimitri Fontaine <dimi...@2ndquadrant.fr> writes: > Robert Haas <robertmh...@gmail.com> writes: >> But on the flip side, I think we're generally a bit more flexible >> about exposing things via C than through the procedural languages. > > Then as Andres proposed, a new function would be available to get the > value, we're not changing the trigger procedure function API in case the > language is C…
I've been updating my github branch with a patch that provides the parsetree to C coded command trigger functions only, as their 5th argument, of type INTERNAL (so that only C coded procs apply). https://github.com/dimitri/postgres/compare/master...command_triggers I still have some cleaning to do before to prepare the next patch version, such as documentation updating and dealing with rewrites of CHECK and DEFAULT column constraints in CREATE TABLE. I had to add support for the T_A_Const parser node, and now I'm about to see about adding support for the T_A_Expr one, but I can't help to wonder how the rewriter could work without them. What is this simple thing I'm missing here, if any? 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
