* New upstream security/bug fix release: (LP: #1116336) - Prevent execution of enum_recv from SQL The function was misdeclared, allowing a simple SQL command to crash the server. In principle an attacker might be able to use it to examine the contents of server memory. Our thanks to Sumit Soni (via Secunia SVCRP) for reporting this issue. (CVE-2013-0255) - See HISTORY/changelog.gz for the other bug fixes.
clause; columns not explicitly modified retain their previous values\&.
51
51
.PP
52
By default,
53
UPDATE
54
will update rows in the specified table and all its subtables\&. If you wish to only update the specific table mentioned, you must use the
55
ONLY
56
clause\&.
57
.PP
58
52
There are two ways to modify a table using information contained in other tables in the database: using sub\-selects, or specifying additional tables in the
59
53
FROM
60
54
clause\&. Which technique is more appropriate depends on the specific circumstances\&.
94
88
.PP
95
89
\fItable\fR
96
90
.RS 4
97
The name (optionally schema\-qualified) of the table to update\&.
91
The name (optionally schema\-qualified) of the table to update\&. If
92
ONLY
93
is specified before the table name, matching rows are updated in the named table only\&. If
94
ONLY
95
is not specified, matching rows are also updated in any tables inheriting from the named table\&. Optionally,
96
*
97
can be specified after the table name to explicitly indicate that descendant tables are included\&.