Rearrange ALTER TABLE syntax processing as per my recent proposal: the
grammar allows ALTER TABLE/INDEX/SEQUENCE/VIEW interchangeably for all
subforms of those commands, and then we sort out what's really legal
at execution time. This allows the ALTER SEQUENCE/VIEW reference pages
to fully document all the ALTER forms available for sequences and views
respectively, and eliminates a longstanding cause of confusion for users.
The net effect is that the following forms are allowed that weren't before:
ALTER SEQUENCE OWNER TO
ALTER VIEW ALTER COLUMN SET/DROP DEFAULT
ALTER VIEW OWNER TO
ALTER VIEW SET SCHEMA
(There's no actual functionality gain here, but formerly you had to say
ALTER TABLE instead.)
Interestingly, the grammar tables actually get smaller, probably because
there are fewer special cases to keep track of.
I did not disallow using ALTER TABLE for these operations. Perhaps we
should, but there's a backwards-compatibility issue if we do; in fact
it would break existing pg_dump scripts. I did however tighten up
ALTER SEQUENCE and ALTER VIEW to reject non-sequences and non-views
in the new cases as well as a couple of cases where they didn't before.
The patch doesn't change pg_dump to use the new syntaxes, either.
alter_sequence.sgml (r1.21 -> r1.22)
alter_view.sgml (r1.3 -> r1.4)
alter.c (r1.28 -> r1.29)
tablecmds.c (r1.256 -> r1.257)
gram.y (r2.615 -> r2.616)
utility.c (r1.293 -> r1.294)
tablecmds.h (r1.39 -> r1.40)
pgsql-committers by date
|Next:||From: Tom Lane||Date: 2008-06-15 01:41:38|
|Subject: pgsql: Fix 64-bit problem in recent patch.|
|Previous:||From: Alvaro Herrera||Date: 2008-06-14 21:59:59|
|Subject: pgsql: In log_filename documentation, mention that strftime is not used |