I tried to pick up this patch to review. It seems to me fine, enough simple and works as explained in the implementation level, apart from reasonability of this feature. (Tom was not 100% agree with this feature 1.5month ago.)
I'm not certain whether the current regression test should be updated, or not. The pg_regress launches psql with -q option, so completionTag is always ignored. Thanks, (2010/11/29 0:14), Marti Raudsepp wrote: > Hi list, > > Often enough when developing PostgreSQL views and functions, I have > pasted the CREATE OR REPLACE commands into the wrong window/shell and > ran them there without realizing that I'm creating a function in the > wrong database, instead of replacing. Currently psql does not provide > any feedback of which action really occured. > > Only after writing this patch I realized that I could instead raise a > NOTICE, like current IF EXISTS/IF NOT EXISTS clauses do. Is that a > better way to solve this? > > This patch returns command tag "CREATE X" or "REPLACE X" for > LANGAUGE/VIEW/RULE/FUNCTION. This is done by passing completionTag to > from ProcessUtility to more functions, and adding a 'bool *didUpdate' > argument to some lower-level functions. I'm not sure if passing back > the status in a bool* is considered good style, but this way all the > functions look consistent. > > Regards, > Marti > -- KaiGai Kohei <kai...@ak.jp.nec.com> -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
