On 2013-11-21 17:14:17 -0500, Peter Eisentraut wrote: > On 11/21/13, 2:35 AM, Pavel Stehule wrote: > > I am feeling, so almost all people prefer > > > > DROP TRIGGER [ IF EXISTS ] name ON table_name [ CASCADE | RESTRICT ]; > > > > Can we live with it? > > Fine with me. > > I think it helps if you consider IF EXISTS an attribute of the command, > not an attribute of the command parameters. > > Now we should be aware that this sort of sets a precedent for ALTER > TABLE IF EXISTS ... DROP ANYTHING ... and similar composite commands.
That already has 2 independent IF EXISTS, so I think the precedence argument goes the other way round. Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
