Sophie

Sophie

distrib > Mageia > 7 > armv7hl > media > core-updates > by-pkgid > 5fea23694c765462b86d6ddf74461eab > files > 915

postgresql9.6-docs-9.6.22-1.mga7.noarch.rpm

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML
><HEAD
><TITLE
>UPDATE</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
REV="MADE"
HREF="mailto:pgsql-docs@postgresql.org"><LINK
REL="HOME"
TITLE="PostgreSQL 9.6.22 Documentation"
HREF="index.html"><LINK
REL="UP"
TITLE="SQL Commands"
HREF="sql-commands.html"><LINK
REL="PREVIOUS"
TITLE="UNLISTEN"
HREF="sql-unlisten.html"><LINK
REL="NEXT"
TITLE="VACUUM"
HREF="sql-vacuum.html"><LINK
REL="STYLESHEET"
TYPE="text/css"
HREF="stylesheet.css"><META
HTTP-EQUIV="Content-Type"
CONTENT="text/html; charset=ISO-8859-1"><META
NAME="creation"
CONTENT="2021-05-18T09:16:10"></HEAD
><BODY
CLASS="REFENTRY"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="4"
ALIGN="center"
VALIGN="bottom"
><A
HREF="index.html"
>PostgreSQL 9.6.22 Documentation</A
></TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="top"
><A
TITLE="UNLISTEN"
HREF="sql-unlisten.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="top"
><A
HREF="sql-commands.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="60%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="20%"
ALIGN="right"
VALIGN="top"
><A
TITLE="VACUUM"
HREF="sql-vacuum.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><H1
><A
NAME="SQL-UPDATE"
></A
>UPDATE</H1
><DIV
CLASS="REFNAMEDIV"
><A
NAME="AEN93266"
></A
><H2
>Name</H2
>UPDATE&nbsp;--&nbsp;update rows of a table</DIV
><DIV
CLASS="REFSYNOPSISDIV"
><A
NAME="AEN93269"
></A
><H2
>Synopsis</H2
><PRE
CLASS="SYNOPSIS"
>[ WITH [ RECURSIVE ] <TT
CLASS="REPLACEABLE"
><I
>with_query</I
></TT
> [, ...] ]
UPDATE [ ONLY ] <TT
CLASS="REPLACEABLE"
><I
>table_name</I
></TT
> [ * ] [ [ AS ] <TT
CLASS="REPLACEABLE"
><I
>alias</I
></TT
> ]
    SET { <TT
CLASS="REPLACEABLE"
><I
>column_name</I
></TT
> = { <TT
CLASS="REPLACEABLE"
><I
>expression</I
></TT
> | DEFAULT } |
          ( <TT
CLASS="REPLACEABLE"
><I
>column_name</I
></TT
> [, ...] ) = ( { <TT
CLASS="REPLACEABLE"
><I
>expression</I
></TT
> | DEFAULT } [, ...] ) |
          ( <TT
CLASS="REPLACEABLE"
><I
>column_name</I
></TT
> [, ...] ) = ( <TT
CLASS="REPLACEABLE"
><I
>sub-SELECT</I
></TT
> )
        } [, ...]
    [ FROM <TT
CLASS="REPLACEABLE"
><I
>from_item</I
></TT
> [, ...] ]
    [ WHERE <TT
CLASS="REPLACEABLE"
><I
>condition</I
></TT
> | WHERE CURRENT OF <TT
CLASS="REPLACEABLE"
><I
>cursor_name</I
></TT
> ]
    [ RETURNING * | <TT
CLASS="REPLACEABLE"
><I
>output_expression</I
></TT
> [ [ AS ] <TT
CLASS="REPLACEABLE"
><I
>output_name</I
></TT
> ] [, ...] ]</PRE
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN93285"
></A
><H2
>Description</H2
><P
>   <TT
CLASS="COMMAND"
>UPDATE</TT
> changes the values of the specified
   columns in all rows that satisfy the condition. Only the columns to
   be modified need be mentioned in the <TT
CLASS="LITERAL"
>SET</TT
> clause;
   columns not explicitly modified retain their previous values.
  </P
><P
>   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 <TT
CLASS="LITERAL"
>FROM</TT
> clause. Which
   technique is more appropriate depends on the specific
   circumstances.
  </P
><P
>   The optional <TT
CLASS="LITERAL"
>RETURNING</TT
> clause causes <TT
CLASS="COMMAND"
>UPDATE</TT
>
   to compute and return value(s) based on each row actually updated.
   Any expression using the table's columns, and/or columns of other
   tables mentioned in <TT
CLASS="LITERAL"
>FROM</TT
>, can be computed.
   The new (post-update) values of the table's columns are used.
   The syntax of the <TT
CLASS="LITERAL"
>RETURNING</TT
> list is identical to that of the
   output list of <TT
CLASS="COMMAND"
>SELECT</TT
>.
  </P
><P
>   You must have the <TT
CLASS="LITERAL"
>UPDATE</TT
> privilege on the table,
   or at least on the column(s) that are listed to be updated.
   You must also have the <TT
CLASS="LITERAL"
>SELECT</TT
>
   privilege on any column whose values are read in the
   <TT
CLASS="REPLACEABLE"
><I
>expressions</I
></TT
> or
   <TT
CLASS="REPLACEABLE"
><I
>condition</I
></TT
>.
  </P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN93303"
></A
><H2
>Parameters</H2
><P
></P
><DIV
CLASS="VARIABLELIST"
><DL
><DT
><TT
CLASS="REPLACEABLE"
><I
>with_query</I
></TT
></DT
><DD
><P
>      The <TT
CLASS="LITERAL"
>WITH</TT
> clause allows you to specify one or more
      subqueries that can be referenced by name in the <TT
CLASS="COMMAND"
>UPDATE</TT
>
      query. See <A
HREF="queries-with.html"
>Section 7.8</A
> and <A
HREF="sql-select.html"
>SELECT</A
>
      for details.
     </P
></DD
><DT
><TT
CLASS="REPLACEABLE"
><I
>table_name</I
></TT
></DT
><DD
><P
>      The name (optionally schema-qualified) of the table to update.
      If <TT
CLASS="LITERAL"
>ONLY</TT
> is specified before the table name, matching rows
      are updated in the named table only.  If <TT
CLASS="LITERAL"
>ONLY</TT
> is not
      specified, matching rows are also updated in any tables inheriting from
      the named table.  Optionally, <TT
CLASS="LITERAL"
>*</TT
> can be specified after the
      table name to explicitly indicate that descendant tables are included.
     </P
></DD
><DT
><TT
CLASS="REPLACEABLE"
><I
>alias</I
></TT
></DT
><DD
><P
>      A substitute name for the target table. When an alias is
      provided, it completely hides the actual name of the table.  For
      example, given <TT
CLASS="LITERAL"
>UPDATE foo AS f</TT
>, the remainder of the
      <TT
CLASS="COMMAND"
>UPDATE</TT
> statement must refer to this table as
      <TT
CLASS="LITERAL"
>f</TT
> not <TT
CLASS="LITERAL"
>foo</TT
>.
     </P
></DD
><DT
><TT
CLASS="REPLACEABLE"
><I
>column_name</I
></TT
></DT
><DD
><P
>      The name of a column in the table named by <TT
CLASS="REPLACEABLE"
><I
>table_name</I
></TT
>.
      The column name can be qualified with a subfield name or array
      subscript, if needed.  Do not include the table's name in the
      specification of a target column &mdash; for example,
      <TT
CLASS="LITERAL"
>UPDATE table_name SET table_name.col = 1</TT
> is invalid.
     </P
></DD
><DT
><TT
CLASS="REPLACEABLE"
><I
>expression</I
></TT
></DT
><DD
><P
>      An expression to assign to the column.  The expression can use the
      old values of this and other columns in the table.
     </P
></DD
><DT
><TT
CLASS="LITERAL"
>DEFAULT</TT
></DT
><DD
><P
>      Set the column to its default value (which will be NULL if no
      specific default expression has been assigned to it).
     </P
></DD
><DT
><TT
CLASS="REPLACEABLE"
><I
>sub-SELECT</I
></TT
></DT
><DD
><P
>      A <TT
CLASS="LITERAL"
>SELECT</TT
> sub-query that produces as many output columns
      as are listed in the parenthesized column list preceding it.  The
      sub-query must yield no more than one row when executed.  If it
      yields one row, its column values are assigned to the target columns;
      if it yields no rows, NULL values are assigned to the target columns.
      The sub-query can refer to old values of the current row of the table
      being updated.
     </P
></DD
><DT
><TT
CLASS="REPLACEABLE"
><I
>from_item</I
></TT
></DT
><DD
><P
>      A table expression allowing columns from other tables to appear in
      the <TT
CLASS="LITERAL"
>WHERE</TT
> condition and update expressions. This
      uses the same syntax as the <A
HREF="sql-select.html#SQL-FROM"
><I
><I
>FROM</I
> Clause</I
></A
> of a <TT
CLASS="COMMAND"
>SELECT</TT
> statement;
      for example, an alias for the table name can be specified.  Do not
      repeat the target table as a <TT
CLASS="REPLACEABLE"
><I
>from_item</I
></TT
>
      unless you intend a self-join (in which case it must appear with
      an alias in the <TT
CLASS="REPLACEABLE"
><I
>from_item</I
></TT
>).
     </P
></DD
><DT
><TT
CLASS="REPLACEABLE"
><I
>condition</I
></TT
></DT
><DD
><P
>      An expression that returns a value of type <TT
CLASS="TYPE"
>boolean</TT
>.
      Only rows for which this expression returns <TT
CLASS="LITERAL"
>true</TT
>
      will be updated.
     </P
></DD
><DT
><TT
CLASS="REPLACEABLE"
><I
>cursor_name</I
></TT
></DT
><DD
><P
>      The name of the cursor to use in a <TT
CLASS="LITERAL"
>WHERE CURRENT OF</TT
>
      condition.  The row to be updated is the one most recently fetched
      from this cursor.  The cursor must be a non-grouping
      query on the <TT
CLASS="COMMAND"
>UPDATE</TT
>'s target table.
      Note that <TT
CLASS="LITERAL"
>WHERE CURRENT OF</TT
> cannot be
      specified together with a Boolean condition.  See
      <A
HREF="sql-declare.html"
>DECLARE</A
>
      for more information about using cursors with
      <TT
CLASS="LITERAL"
>WHERE CURRENT OF</TT
>.
     </P
></DD
><DT
><TT
CLASS="REPLACEABLE"
><I
>output_expression</I
></TT
></DT
><DD
><P
>      An expression to be computed and returned by the <TT
CLASS="COMMAND"
>UPDATE</TT
>
      command after each row is updated.  The expression can use any
      column names of the table named by <TT
CLASS="REPLACEABLE"
><I
>table_name</I
></TT
>
      or table(s) listed in <TT
CLASS="LITERAL"
>FROM</TT
>.
      Write <TT
CLASS="LITERAL"
>*</TT
> to return all columns.
     </P
></DD
><DT
><TT
CLASS="REPLACEABLE"
><I
>output_name</I
></TT
></DT
><DD
><P
>      A name to use for a returned column.
     </P
></DD
></DL
></DIV
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN93396"
></A
><H2
>Outputs</H2
><P
>   On successful completion, an <TT
CLASS="COMMAND"
>UPDATE</TT
> command returns a command
   tag of the form
</P><PRE
CLASS="SCREEN"
>UPDATE <TT
CLASS="REPLACEABLE"
><I
>count</I
></TT
></PRE
><P>
   The <TT
CLASS="REPLACEABLE"
><I
>count</I
></TT
> is the number
   of rows updated, including matched rows whose values did not change.
   Note that the number may be less than the number of rows that matched
   the <TT
CLASS="REPLACEABLE"
><I
>condition</I
></TT
> when
   updates were suppressed by a <TT
CLASS="LITERAL"
>BEFORE UPDATE</TT
> trigger.  If
   <TT
CLASS="REPLACEABLE"
><I
>count</I
></TT
> is 0, no rows were
   updated by the query (this is not considered an error).
  </P
><P
>   If the <TT
CLASS="COMMAND"
>UPDATE</TT
> command contains a <TT
CLASS="LITERAL"
>RETURNING</TT
>
   clause, the result will be similar to that of a <TT
CLASS="COMMAND"
>SELECT</TT
>
   statement containing the columns and values defined in the
   <TT
CLASS="LITERAL"
>RETURNING</TT
> list, computed over the row(s) updated by the
   command.
  </P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN93411"
></A
><H2
>Notes</H2
><P
>   When a <TT
CLASS="LITERAL"
>FROM</TT
> clause is present, what essentially happens
   is that the target table is joined to the tables mentioned in the
   <TT
CLASS="REPLACEABLE"
><I
>from_item</I
></TT
> list, and each output row of the join
   represents an update operation for the target table.  When using
   <TT
CLASS="LITERAL"
>FROM</TT
> you should ensure that the join
   produces at most one output row for each row to be modified.  In
   other words, a target row shouldn't join to more than one row from
   the other table(s).  If it does, then only one of the join rows
   will be used to update the target row, but which one will be used
   is not readily predictable.
  </P
><P
>   Because of this indeterminacy, referencing other tables only within
   sub-selects is safer, though often harder to read and slower than
   using a join.
  </P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN93418"
></A
><H2
>Examples</H2
><P
>   Change the word <TT
CLASS="LITERAL"
>Drama</TT
> to <TT
CLASS="LITERAL"
>Dramatic</TT
> in the
   column <TT
CLASS="STRUCTFIELD"
>kind</TT
> of the table <TT
CLASS="STRUCTNAME"
>films</TT
>:

</P><PRE
CLASS="PROGRAMLISTING"
>UPDATE films SET kind = 'Dramatic' WHERE kind = 'Drama';</PRE
><P>
  </P
><P
>   Adjust temperature entries and reset precipitation to its default
   value in one row of the table <TT
CLASS="STRUCTNAME"
>weather</TT
>:

</P><PRE
CLASS="PROGRAMLISTING"
>UPDATE weather SET temp_lo = temp_lo+1, temp_hi = temp_lo+15, prcp = DEFAULT
  WHERE city = 'San Francisco' AND date = '2003-07-03';</PRE
><P>
  </P
><P
>   Perform the same operation and return the updated entries:

</P><PRE
CLASS="PROGRAMLISTING"
>UPDATE weather SET temp_lo = temp_lo+1, temp_hi = temp_lo+15, prcp = DEFAULT
  WHERE city = 'San Francisco' AND date = '2003-07-03'
  RETURNING temp_lo, temp_hi, prcp;</PRE
><P>
  </P
><P
>   Use the alternative column-list syntax to do the same update:
</P><PRE
CLASS="PROGRAMLISTING"
>UPDATE weather SET (temp_lo, temp_hi, prcp) = (temp_lo+1, temp_lo+15, DEFAULT)
  WHERE city = 'San Francisco' AND date = '2003-07-03';</PRE
><P>
  </P
><P
>   Increment the sales count of the salesperson who manages the
   account for Acme Corporation, using the <TT
CLASS="LITERAL"
>FROM</TT
>
   clause syntax:
</P><PRE
CLASS="PROGRAMLISTING"
>UPDATE employees SET sales_count = sales_count + 1 FROM accounts
  WHERE accounts.name = 'Acme Corporation'
  AND employees.id = accounts.sales_person;</PRE
><P>
  </P
><P
>   Perform the same operation, using a sub-select in the
   <TT
CLASS="LITERAL"
>WHERE</TT
> clause:
</P><PRE
CLASS="PROGRAMLISTING"
>UPDATE employees SET sales_count = sales_count + 1 WHERE id =
  (SELECT sales_person FROM accounts WHERE name = 'Acme Corporation');</PRE
><P>
  </P
><P
>   Update contact names in an accounts table to match the currently assigned
   salesmen:
</P><PRE
CLASS="PROGRAMLISTING"
>UPDATE accounts SET (contact_first_name, contact_last_name) =
    (SELECT first_name, last_name FROM salesmen
     WHERE salesmen.id = accounts.sales_id);</PRE
><P>
   A similar result could be accomplished with a join:
</P><PRE
CLASS="PROGRAMLISTING"
>UPDATE accounts SET contact_first_name = first_name,
                    contact_last_name = last_name
  FROM salesmen WHERE salesmen.id = accounts.sales_id;</PRE
><P>
   However, the second query may give unexpected results
   if <TT
CLASS="STRUCTNAME"
>salesmen</TT
>.<TT
CLASS="STRUCTFIELD"
>id</TT
> is not a unique key, whereas
   the first query is guaranteed to raise an error if there are multiple
   <TT
CLASS="STRUCTFIELD"
>id</TT
> matches.  Also, if there is no match for a particular
   <TT
CLASS="STRUCTNAME"
>accounts</TT
>.<TT
CLASS="STRUCTFIELD"
>sales_id</TT
> entry, the first query
   will set the corresponding name fields to NULL, whereas the second query
   will not update that row at all.
  </P
><P
>   Update statistics in a summary table to match the current data:
</P><PRE
CLASS="PROGRAMLISTING"
>UPDATE summary s SET (sum_x, sum_y, avg_x, avg_y) =
    (SELECT sum(x), sum(y), avg(x), avg(y) FROM data d
     WHERE d.group_id = s.group_id);</PRE
><P>
  </P
><P
>   Attempt to insert a new stock item along with the quantity of stock. If
   the item already exists, instead update the stock count of the existing
   item. To do this without failing the entire transaction, use savepoints:
</P><PRE
CLASS="PROGRAMLISTING"
>BEGIN;
-- other operations
SAVEPOINT sp1;
INSERT INTO wines VALUES('Chateau Lafite 2003', '24');
-- Assume the above fails because of a unique key violation,
-- so now we issue these commands:
ROLLBACK TO sp1;
UPDATE wines SET stock = stock + 24 WHERE winename = 'Chateau Lafite 2003';
-- continue with other operations, and eventually
COMMIT;</PRE
><P>
  </P
><P
>   Change the <TT
CLASS="STRUCTFIELD"
>kind</TT
> column of the table
   <TT
CLASS="STRUCTNAME"
>films</TT
> in the row on which the cursor
   <TT
CLASS="LITERAL"
>c_films</TT
> is currently positioned:
</P><PRE
CLASS="PROGRAMLISTING"
>UPDATE films SET kind = 'Dramatic' WHERE CURRENT OF c_films;</PRE
><P></P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN93456"
></A
><H2
>Compatibility</H2
><P
>   This command conforms to the <ACRONYM
CLASS="ACRONYM"
>SQL</ACRONYM
> standard, except
   that the <TT
CLASS="LITERAL"
>FROM</TT
> and <TT
CLASS="LITERAL"
>RETURNING</TT
> clauses
   are <SPAN
CLASS="PRODUCTNAME"
>PostgreSQL</SPAN
> extensions, as is the ability
   to use <TT
CLASS="LITERAL"
>WITH</TT
> with <TT
CLASS="COMMAND"
>UPDATE</TT
>.
  </P
><P
>   Some other database systems offer a <TT
CLASS="LITERAL"
>FROM</TT
> option in which
   the target table is supposed to be listed again within <TT
CLASS="LITERAL"
>FROM</TT
>.
   That is not how <SPAN
CLASS="PRODUCTNAME"
>PostgreSQL</SPAN
> interprets
   <TT
CLASS="LITERAL"
>FROM</TT
>.  Be careful when porting applications that use this
   extension.
  </P
><P
>   According to the standard, the source value for a parenthesized sub-list of
   column names can be any row-valued expression yielding the correct number
   of columns.  <SPAN
CLASS="PRODUCTNAME"
>PostgreSQL</SPAN
> only allows the source
   value to be a parenthesized list of expressions or a
   sub-<TT
CLASS="LITERAL"
>SELECT</TT
>.  An individual column's updated value can be
   specified as <TT
CLASS="LITERAL"
>DEFAULT</TT
> in the list-of-expressions case, but not
   inside a sub-<TT
CLASS="LITERAL"
>SELECT</TT
>.
  </P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="sql-unlisten.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="sql-vacuum.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>UNLISTEN</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="sql-commands.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>VACUUM</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

Perl :: Catalyst :: PostgreSQL :: RPM Valid HTML 4.01 Transitional