On Sat, Mar 3, 2012 at 9:23 PM, Alvaro Herrera <alvhe...@commandprompt.com> wrote: > Uh! Now that I read this I realize that what you're supposed to give to > CHECK TRIGGER is the trigger name, not the function name! In that > light, using CHECK FUNCTION for this doesn't make a lot of sense. > > Okay, CHECK TRIGGER it is.
I confess to some bafflement about why we need dedicated syntax for this, or even any kind of core support at all. What would be wrong with defining a function that takes regprocedure as an argument and does whatever? Sure, it's nicer syntax, but we've repeatedly rejected patches that only provided nicer syntax on the grounds that syntax is not free, and therefore syntax alone is not a reason to change the core grammar. What makes this case different? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
