| From: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
|---|---|
| To: | Bret Hughes <bhughes(at)elevating(dot)com> |
| Cc: | postgresql sql list <pgsql-sql(at)postgresql(dot)org> |
| Subject: | Re: what does ONLY do |
| Date: | 2005-02-19 03:15:30 |
| Message-ID: | 20050218191259.I39081@megazone.bigpanda.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
On Fri, 18 Feb 2005, Bret Hughes wrote:
> I can't seem to find an explanation of what adding ONLY does for an sql
> statement for instance :
>
> ALTER TABLE [ONLY] ADD COLUMN ...
>
> or what ever. Does anyone have a pointer to docs on this. I am simply
> curious since there is obviously something I am missing.
Using the ALTER TABLE page as an example...
name
The name (possibly schema-qualified) of an existing table to alter. If
ONLY is specified, only that table is altered. If ONLY is not specified,
the table and all its descendant tables (if any) are updated. * can be
appended to the table name to indicate that descendant tables are to be
altered, but in the current version, this is the default behavior. (In
releases before 7.1, ONLY was the default behavior. The default can be
altered by changing the configuration parameter sql_inheritance.)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bret Hughes | 2005-02-19 04:08:12 | Re: what does ONLY do |
| Previous Message | Bret Hughes | 2005-02-19 01:59:54 | what does ONLY do |