On Wed, Oct 19, 2011 at 10:40 PM, Tom Lane <t...@sss.pgh.pa.us> wrote:
> Josh Kupershmidt <schmi...@gmail.com> writes:
>> Incidentally, I was wondering what the heck was up with a clause like this:
>> else if (pg_strcasecmp(prev_wd, "EXECUTE") == 0 &&
>> pg_strcasecmp(prev2_wd, "EXECUTE") == 0)
>
> Hmm, maybe || was meant not && ? It seems pretty unlikely that the
> above test would ever trigger on valid SQL input.
Well, changing '&&' to '||' breaks the stated comment of the patch, namely:
/* must not match CREATE TRIGGER ... EXECUTE PROCEDURE */
I assume this is an accepted quirk of previous_word() since we have
this existing similar code:
/* DROP, but watch out for DROP embedded in other commands */
/* complete with something you can drop */
else if (pg_strcasecmp(prev_wd, "DROP") == 0 &&
pg_strcasecmp(prev2_wd, "DROP") == 0)
and the patch does seem to auto-complete a beginning EXECUTE
correctly. We could probably use a comment somewhere explaining this
quirk.
Josh
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
