Some small polishing of Mark Hollomon's cleanup of DROP command: might
authorTom Lane <tgl@sss.pgh.pa.us>
Sun, 22 Oct 2000 23:32:48 +0000 (23:32 +0000)
committerTom Lane <tgl@sss.pgh.pa.us>
Sun, 22 Oct 2000 23:32:48 +0000 (23:32 +0000)
commit9ace03183c56ca3474679bc56316e962d0af4b81
treefd385e10d8d458985f9410ccc4170ae6fa5acb26
parentee28d8b3d509593c980b8cdcc5a8943a429bdc9b
Some small polishing of Mark Hollomon's cleanup of DROP command: might
as well allow DROP multiple INDEX, RULE, TYPE as well.  Add missing
CommandCounterIncrement to DROP loop, which could cause trouble otherwise
with multiple DROP of items affecting same catalog entries.  Try to
bring a little consistency to various error messages using 'does not exist',
'nonexistent', etc --- I standardized on 'does not exist' since that's
what the vast majority of the existing uses seem to be.
18 files changed:
doc/src/sgml/ref/drop_index.sgml
doc/src/sgml/ref/drop_rule.sgml
doc/src/sgml/ref/drop_sequence.sgml
doc/src/sgml/ref/drop_table.sgml
doc/src/sgml/ref/drop_type.sgml
doc/src/sgml/ref/drop_view.sgml
src/backend/catalog/heap.c
src/backend/catalog/pg_operator.c
src/backend/commands/indexcmds.c
src/backend/commands/rename.c
src/backend/parser/gram.y
src/backend/tcop/utility.c
src/include/nodes/nodes.h
src/test/regress/expected/errors.out
src/test/regress/expected/foreign_key.out
src/test/regress/expected/inet.out
src/test/regress/expected/plpgsql.out
src/test/regress/sql/plpgsql.sql