<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.49.2.5 2000/06/05 10:59:16 momjian Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.49.2.6 2000/06/14 13:18:59 thomas Exp $
-->
<chapter id="release">
<title>Release Notes</title>
-<sect1>
-<title>Release 7.0.2</title>
-<!--
-<docinfo>
-<authorgroup>
-<author>
-<firstname>Bruce</firstname>
-<surname>Momjian</surname>
-</author>
-</authorgroup>
-<date>2000-06-05</date>
-</docinfo>
--->
+ <sect1>
+ <title>Release 7.0.2</title>
+ <!--
+ <docinfo>
+ <firstname>Bruce</firstname>
+ <surname>Momjian</surname>
+ </author>
+ </authorgroup>
+ <date>2000-06-05</date>
+ </docinfo>
+ -->
-<para>
-2000-06-05
-</para>
-<para>
-This is a repackaging of 7.0.1 with added documentation.
-</para>
+ <para>
+ Release date 2000-06-05. This is a repackaging of 7.0.1 with added documentation.
+ </para>
-<sect2>
-<title>Migration to v7.0.2</title>
+ <sect2>
+ <title>Migration to v7.0.2</title>
-<para>
-A dump/restore is <emphasis>not</emphasis> required for those running
-7.*.
-</para>
-</sect2>
-<sect2>
-<title>Changes</title>
+ <para>
+ A dump/restore is <emphasis>not</emphasis> required for those running
+ v7.*.
+ </para>
+ </sect2>
-<para>
-<programlisting>
+ <sect2>
+ <title>Changes</title>
+
+ <para>
+ <programlisting>
Added documentation to tarball.
-</programlisting>
-</para>
-</sect2>
-</sect1>
+ </programlisting>
+ </para>
+ </sect2>
+ </sect1>
-<sect1>
-<title>Release 7.0.1</title>
-<!--
-<docinfo>
-<authorgroup>
-<author>
-<firstname>Bruce</firstname>
-<surname>Momjian</surname>
-</author>
-</authorgroup>
-<date>2000-06-01</date>
-</docinfo>
--->
+ <sect1>
+ <title>Release 7.0.1</title>
+ <!--
+ <docinfo>
+ <firstname>Bruce</firstname>
+ <surname>Momjian</surname>
+ </author>
+ </authorgroup>
+ <date>2000-06-01</date>
+ </docinfo>
+ -->
-<para>
-2000-06-01
-</para>
-<para>
-This is basically a cleanup release for 7.0.
-</para>
+ <para>
+ Release date 2000-06-01.
+ This is a cleanup release for 7.0.
+ </para>
+ <sect2>
+ <title>Migration to v7.0.1</title>
-<sect2>
-<title>Migration to v7.0.1</title>
+ <para>
+ A dump/restore is <emphasis>not</emphasis> required for those running
+ v7.0.
+ </para>
+ </sect2>
-<para>
-A dump/restore is <emphasis>not</emphasis> required for those running
-7.0.
-</para>
-</sect2>
-<sect2>
-<title>Changes</title>
+ <sect2>
+ <title>Changes</title>
-<para>
-<programlisting>
Fix many CLUSTER failures (Tom)
Allow ALTER TABLE RENAME works on indexes (Tom)
Fix plpgsql to handle datetime->timestamp and timespan->interval (Bruce)
Fix problem with quoted indexes that are too long (Tom)
JDBC ResultSet.getTimestamp() fix (Gregory Krasnow & Floyd Marinescu)
ecpg changes (Michael)
-</programlisting>
-</para>
-</sect2>
-</sect1>
-
+ </programlisting>
+ </para>
+ </sect2>
+ </sect1>
<sect1>
<title>Release 7.0</title>
</docinfo>
-->
<para>
-2000-05-08
- </para>
- <para>
+ Released 2000-05-08.
This release contains improvements in many areas, demonstrating
the continued growth of <productname>PostgreSQL</productname>.
There are more improvements and fixes in 7.0 than in any previous
</sect2>
<sect2>
+ <title>Changes</title>
+
<para>
<programlisting>
Bug Fixes
</sect2>
</sect1>
-<sect1>
-<title>Release 6.5.3</title>
-<!--
-<docinfo>
-<authorgroup>
-<author>
-<firstname>Bruce</firstname>
-<surname>Momjian</surname>
-</author>
-</authorgroup>
-<date>1999-10-13</date>
-</docinfo>
--->
+ <sect1>
+ <title>Release 6.5.3</title>
+ <!--
+ <docinfo>
+ <firstname>Bruce</firstname>
+ <surname>Momjian</surname>
+ </author>
+ </authorgroup>
+ <date>1999-10-13</date>
+ </docinfo>
+ -->
-<para>
-1999-10-13
-</para>
-<para>
-This is basically a cleanup release for 6.5.2. We have added a new
-pgaccess that was missing in 6.5.2, and installed an NT-specific fix.
-</para>
+ <para>
+ Released 1999-10-13.
+ This is basically a cleanup release for 6.5.2. We have added a new
+ pgaccess that was missing in 6.5.2, and installed an NT-specific fix.
+ </para>
-<sect2>
-<title>Migration to v6.5.3</title>
+ <sect2>
+ <title>Migration to v6.5.3</title>
-<para>
-A dump/restore is <emphasis>not</emphasis> required for those running
-6.5.*.
-</para>
-</sect2>
-<sect2>
-<title>Changes</title>
+ A dump/restore is <emphasis>not</emphasis> required for those running
+ 6.5.*.
+ </para>
+ </sect2>
+ <sect2>
+ <title>Changes</title>
-<para>
-<programlisting>
Updated version of pgaccess 0.98
NT-specific patch
Fix dumping rules on inherited tables
-</programlisting>
-</para>
-</sect2>
-</sect1>
+ </programlisting>
+ </para>
+ </sect2>
+ </sect1>
-<sect1>
-<title>Release 6.5.2</title>
-<!--
-<docinfo>
-<authorgroup>
-<author>
-<firstname>Bruce</firstname>
-<surname>Momjian</surname>
-</author>
-</authorgroup>
-<date>1999-09-15</date>
-</docinfo>
--->
+ <sect1>
+ <title>Release 6.5.2</title>
+ <!--
+ <docinfo>
+ <firstname>Bruce</firstname>
+ <surname>Momjian</surname>
+ </author>
+ </authorgroup>
+ <date>1999-09-15</date>
+ </docinfo>
+ -->
-<para>
-1999-09-15
-</para>
-<para>
-This is basically a cleanup release for 6.5.1. We have fixed a variety of
-problems reported by 6.5.1 users.
-</para>
+ <para>
+ Released 1999-09-15.
+ This is basically a cleanup release for 6.5.1. We have fixed a variety of
+ problems reported by 6.5.1 users.
+ </para>
-<sect2>
-<title>Migration to v6.5.2</title>
+ <sect2>
+ <title>Migration to v6.5.2</title>
-<para>
-A dump/restore is <emphasis>not</emphasis> required for those running
-6.5.*.
-</para>
-</sect2>
-<sect2>
-<title>Changes</title>
+ <para>
+ A dump/restore is <emphasis>not</emphasis> required for those running
+ 6.5.*.
+ </para>
+ </sect2>
-<para>
-<programlisting>
+ <sect2>
+ <title>Changes</title>
+
+ <para>
+ <programlisting>
subselect+CASE fixes(Tom)
Add SHLIB_LINK setting for solaris_i386 and solaris_sparc ports(Daren Sefcik)
Fixes for CASE in WHERE join clauses(Tom)
when reach end of pattern before end of text(Tom)
Repair incorrect cleanup of heap memory allocation during transaction abort(Tom)
Updated version of pgaccess 0.98
-</programlisting>
-</para>
-</sect2>
-</sect1>
-
+ </programlisting>
+ </para>
+ </sect2>
+ </sect1>
-<sect1>
-<title>Release 6.5.1</title>
-<!--
-<docinfo>
-<authorgroup>
-<author>
-<firstname>Bruce</firstname>
-<surname>Momjian</surname>
-</author>
-</authorgroup>
-<date>1999-07-15</date>
-</docinfo>
--->
+ <sect1>
+ <title>Release 6.5.1</title>
+ <!--
+ <docinfo>
+ <firstname>Bruce</firstname>
+ <surname>Momjian</surname>
+ </author>
+ </authorgroup>
+ <date>1999-07-15</date>
+ </docinfo>
+ -->
-<para>
-1999-07-15
-</para>
-<para>
-This is basically a cleanup release for 6.5. We have fixed a variety of
-problems reported by 6.5 users.
-</para>
+ Released 1999-07-15.
+ </para>
+ This is basically a cleanup release for 6.5. We have fixed a variety of
+ problems reported by 6.5 users.
+ </para>
+ <sect2>
+ <title>Migration to v6.5.1</title>
-<sect2>
-<title>Migration to v6.5.1</title>
+ <para>
+ A dump/restore is <emphasis>not</emphasis> required for those running
+ 6.5.
+ </para>
+ </sect2>
-<para>
-A dump/restore is <emphasis>not</emphasis> required for those running
-6.5.
-</para>
-</sect2>
-<sect2>
-<title>Changes</title>
+ <sect2>
+ <title>Changes</title>
-<para>
-<programlisting>
Add NT README file
Portability fixes for linux_ppc, Irix, linux_alpha, OpenBSD, alpha
Remove QUERY_LIMIT, use SELECT...LIMIT
Fixed glitches affecting GROUP BY in subselects(Tom)
Fix some compiler warnings (Tomoaki Nishiyama)
Add Win1250 (Czech) support (Pavel Behal)
-</programlisting>
-</para>
-</sect2>
-</sect1>
-
+ </programlisting>
+ </para>
+ </sect2>
+ </sect1>
-<sect1>
-<title>Release 6.5</title>
-<!--
-<docinfo>
-<authorgroup>
-<author>
-<firstname>Bruce</firstname>
-<surname>Momjian</surname>
-</author>
-</authorgroup>
-<date>1999-06-09</date>
-</docinfo>
--->
+ <sect1>
+ <title>Release 6.5</title>
+ <!--
+ <docinfo>
+ <firstname>Bruce</firstname>
+ <surname>Momjian</surname>
+ </author>
+ </authorgroup>
+ <date>1999-06-09</date>
+ </docinfo>
+ -->
<para>
-1999-06-09
-</para>
-<para>
+ Released 1999-06-09.
This release marks a major step in the development team's mastery of the source
code we inherited from Berkeley. You will see we are now easily adding
major features, thanks to the increasing size and experience of our
</sect2>
<sect2>
+ <title>Changes</title>
+
<para>
<programlisting>
Bug Fixes
previous release of <productname>Postgres</productname>.
</para>
</sect2>
-<sect2>
-<para>
-<programlisting>
+ <sect2>
+<title>Changes</title>
+
+ <para>
+ <programlisting>
Bug Fixes
---------
Fix for a tiny memory leak in PQsetdb/PQfinish(Bryan)
refer to the installation and migration instructions for v6.3.
</para>
-<sect2>
+ <sect2>
+ <title>Changes</title>
-<para>
-<programlisting>
-Changes
--------
+ <para>
+ <programlisting>
Configure detection improvements for tcl/tk(Brook Milligan, Alvin)
Manual page improvements(Bruce)
BETWEEN and LIKE fix(Thomas)
Remove DISTDIR(Bruce)
Makefile dependency cleanup(Jeroen van Vianen)
ASSERT fixes(Bruce)
-</programlisting>
-</para>
-</sect2>
-</sect1>
-<sect1>
-<title>Release 6.3.1</title>
-<!--
-<docinfo>
-<authorgroup>
-<author>
-<firstname>Bruce</firstname>
-<surname>Momjian</surname>
-</author>
-</authorgroup>
-<date>1998-03-23</date>
-</docinfo>
--->
+ </programlisting>
+ </para>
+ </sect2>
+ </sect1>
-<para>
-1998-03-23
-</para>
-<para>
-Summary:
+ <sect1>
+ <title>Release 6.3.1</title>
+ <!--
+ <docinfo>
+ <authorgroup>
+ <author>
+ <firstname>Bruce</firstname>
+ <surname>Momjian</surname>
+ </author>
+ </authorgroup>
+ <date>1998-03-23</date>
+ </docinfo>
+ -->
+
+ <para>
+ Released 1998-03-23.
+ Summary:
<itemizedlist>
<listitem>
refer to the installation and migration instructions for v6.3.
</para>
-<sect2>
+ <sect2>
+ <title>Changes</title>
-<para>
-<programlisting>
-Changes
--------
+ <para>
+ <programlisting>
ecpg cleanup/fixes, now version 1.1(Michael Meskes)
pg_user cleanup(Bruce)
large object fix for pg_dump and tclsh (alvin)
Fix for text arrays containing quotes(Doug Gibson)
Solaris compile fix(Albert Chin-A-Young)
Better identify tcl and tk libs and includes(Bruce)
-</programlisting>
-</para>
-</sect2>
-</sect1>
-<sect1>
-<title>Release 6.3</title>
-<!--
-<docinfo>
-<authorgroup>
-<author>
-<firstname>Bruce</firstname>
-<surname>Momjian</surname>
-</author>
-</authorgroup>
-<date>1998-03-01</date>
-</docinfo>
--->
+ </programlisting>
+ </para>
+ </sect2>
+ </sect1>
-<para>
-1998-03-01
-</para>
-<para>
-There are <emphasis>many</emphasis> new features and improvements in this release.
-Here is a brief, incomplete summary:
+ <sect1>
+ <title>Release 6.3</title>
+ <!--
+ <docinfo>
+ <authorgroup>
+ <author>
+ <firstname>Bruce</firstname>
+ <surname>Momjian</surname>
+ </author>
+ </authorgroup>
+ <date>1998-03-01</date>
+ </docinfo>
+ -->
-<itemizedlist>
-<listitem>
-<para>
-Many new SQL features, including
-full <acronym>SQL92</acronym> subselect capability
-(everything is here but target-list subselects).
-</para>
-</listitem>
+ <para>
+ Released 1998-03-01.
+ There are <emphasis>many</emphasis> new features and improvements in this release.
+ Here is a brief, incomplete summary:
-<listitem>
-<para>
-Support for client-side environment variables to specify time zone and date style.
-</para>
-</listitem>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Many new SQL features, including
+ full <acronym>SQL92</acronym> subselect capability
+ (everything is here but target-list subselects).
+ </para>
+ </listitem>
-<listitem>
-<para>
-Socket interface for client/server connection. This is the default now
-so you may need to start <application>postmaster</application> with the
-<option>-i</option> flag.
-</para>
-</listitem>
+ <listitem>
+ <para>
+ Support for client-side environment variables to specify time zone and date style.
+ </para>
+ </listitem>
-<listitem>
-<para>
-Better password authorization mechanisms. Default table permissions have changed.
-</para>
-</listitem>
+ <listitem>
+ <para>
+ Socket interface for client/server connection. This is the default now
+ so you may need to start <application>postmaster</application> with the
+ <option>-i</option> flag.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Better password authorization mechanisms. Default table permissions have changed.
+ </para>
+ </listitem>
<listitem>
<para>
has been removed. Performance has been improved.
</para>
</listitem>
+ </itemizedlist>
+ </para>
-</itemizedlist>
-</para>
-
-<note>
-<para>
-Bruce Momjian wrote the following notes to introduce the new release.
-</para>
-</note>
+ <note>
+ <para>
+ Bruce Momjian wrote the following notes to introduce the new release.
+ </para>
+ </note>
-<para>
-There are some general 6.3 issues that I want to mention. These are
-only the big items that can not be described in one sentence. A review
-of the detailed changes list is still needed.
-</para>
-<para>
-First, we now have subselects. Now that we have them, I would like to
-mention that without subselects, SQL is a very limited language.
-Subselects are a major feature, and you should review your code for
-places where subselects provide a better solution for your queries. I
-think you will find that there are more uses for subselects than you may
-think. Vadim has put us on the big SQL map with subselects, and fully
-functional ones too. The only thing you can't do with subselects is to
-use them in the target list.
-</para>
-<para>
-Second, 6.3 uses unix domain sockets rather than TCP/IP by default. To
-enable connections from other machines, you have to use the new
-postmaster -i option, and of course edit pg_hba.conf. Also, for this
-reason, the format of pg_hba.conf has changed.
-</para>
-<para>
-Third, char() fields will now allow faster access than varchar() or
-text. Specifically, the text and varchar() have a penalty for access to
-any columns after the first column of this type. char() used to also
-have this access penalty, but it no longer does. This may suggest that
-you redesign some of your tables, especially if you have short character
-columns that you have defined as varchar() or text. This and other
-changes make 6.3 even faster than earlier releases.
-</para>
-<para>
-We now have passwords definable independent of any Unix file. There are
-new SQL USER commands. See the pg_hba.conf manual page for more
-information. There is a new table, pg_shadow, which is used to store
-user information and user passwords, and it by default only SELECT-able
-by the postgres super-user. pg_user is now a view of pg_shadow, and is
-SELECT-able by PUBLIC. You should keep using pg_user in your
-application without changes.
-</para>
-<para>
-User-created tables now no longer have SELECT permission to PUBLIC by
-default. This was done because the ANSI standard requires it. You can
-of course GRANT any permissions you want after the table is created.
-System tables continue to be SELECT-able by PUBLIC.
-</para>
-<para>
-We also have real deadlock detection code. No more sixty-second
-timeouts. And the new locking code implements a FIFO better, so there
-should be less resource starvation during heavy use.
-</para>
-<para>
-Many complaints have been made about inadequate documenation in previous
-releases. Thomas has put much effort into many new manuals for this
-release. Check out the doc/ directory.
-</para>
-<para>
-For performance reasons, time travel is gone, but can be implemented
-using triggers (see pgsql/contrib/spi/README). Please check out the new
-\d command for types, operators, etc. Also, views have their own
-permissions now, not based on the underlying tables, so permissions on
-them have to be set separately. Check /pgsql/interfaces for some new
-ways to talk to <productname>Postgres</productname>.
-</para>
-<para>
-This is the first release that really required an explanation for
-existing users. In many ways, this was necessary because the new
-release removes many limitations, and the work-arounds people were using
-are no longer needed.
-</para>
+ There are some general 6.3 issues that I want to mention. These are
+ only the big items that can not be described in one sentence. A review
+ of the detailed changes list is still needed.
+ </para>
+ First, we now have subselects. Now that we have them, I would like to
+ mention that without subselects, SQL is a very limited language.
+ Subselects are a major feature, and you should review your code for
+ places where subselects provide a better solution for your queries. I
+ think you will find that there are more uses for subselects than you may
+ think. Vadim has put us on the big SQL map with subselects, and fully
+ functional ones too. The only thing you can't do with subselects is to
+ use them in the target list.
+ </para>
+ Second, 6.3 uses unix domain sockets rather than TCP/IP by default. To
+ enable connections from other machines, you have to use the new
+ postmaster -i option, and of course edit pg_hba.conf. Also, for this
+ reason, the format of pg_hba.conf has changed.
+ </para>
+ Third, char() fields will now allow faster access than varchar() or
+ text. Specifically, the text and varchar() have a penalty for access to
+ any columns after the first column of this type. char() used to also
+ have this access penalty, but it no longer does. This may suggest that
+ you redesign some of your tables, especially if you have short character
+ columns that you have defined as varchar() or text. This and other
+ changes make 6.3 even faster than earlier releases.
+ </para>
+ We now have passwords definable independent of any Unix file. There are
+ new SQL USER commands. See the pg_hba.conf manual page for more
+ information. There is a new table, pg_shadow, which is used to store
+ user information and user passwords, and it by default only SELECT-able
+ by the postgres super-user. pg_user is now a view of pg_shadow, and is
+ SELECT-able by PUBLIC. You should keep using pg_user in your
+ application without changes.
+ </para>
+ User-created tables now no longer have SELECT permission to PUBLIC by
+ default. This was done because the ANSI standard requires it. You can
+ of course GRANT any permissions you want after the table is created.
+ System tables continue to be SELECT-able by PUBLIC.
+ </para>
+ We also have real deadlock detection code. No more sixty-second
+ timeouts. And the new locking code implements a FIFO better, so there
+ should be less resource starvation during heavy use.
+ </para>
+ Many complaints have been made about inadequate documenation in previous
+ releases. Thomas has put much effort into many new manuals for this
+ release. Check out the doc/ directory.
+ </para>
+ For performance reasons, time travel is gone, but can be implemented
+ using triggers (see pgsql/contrib/spi/README). Please check out the new
+ \d command for types, operators, etc. Also, views have their own
+ permissions now, not based on the underlying tables, so permissions on
+ them have to be set separately. Check /pgsql/interfaces for some new
+
ways to talk to <productname>Postgres</productname>.
+ </para>
+ This is the first release that really required an explanation for
+ existing users. In many ways, this was necessary because the new
+ release removes many limitations, and the work-arounds people were using
+ are no longer needed.
+ </para>
-<sect2>
-<title>Migration to v6.3</title>
+ <sect2>
+ <title>Migration to v6.3</title>
-<para>
-A dump/restore using <application>pg_dump</application>
-or <application>pg_dumpall</application>
-is required for those wishing to migrate data from any
-previous release of <productname>Postgres</productname>.
-</para>
-</sect2>
+
A dump/restore using <application>pg_dump</application>
+
or <application>pg_dumpall</application>
+ is required for those wishing to migrate data from any
+
previous release of <productname>Postgres</productname>.
+ </para>
+ </sect2>
-<sect2>
+ <sect2>
+ <title>Changes</title>
-<para>
-<programlisting>
Bug Fixes
---------
Fix binary cursors broken by MOVE implementation(Vadim)
This will need to be done to every existing database, including template1.
</para>
</sect2>
-<sect2>
-<para>
-<programlisting>
-Changes
--------
+ <sect2>
+ <title>Changes</title>
+
+ <para>
+ <programlisting>
Allow TIME and TYPE column names(Thomas)
Allow larger range of true/false as boolean values(Thomas)
Support output of "now" and "current"(Thomas)
Fix for specifying a column twice in ORDER/GROUP BY(Vadim)
Documented new libpq function to return affected rows, PQcmdTuples(Bruce)
Trigger function for inserting user names for INSERT/UPDATE(Brook Milligan)
-</programlisting>
-</para>
-</sect2>
-</sect1>
+ </programlisting>
+ </para>
+ </sect2>
+ </sect1>
<sect1>
<title>Release 6.2</title>
</para>
</sect2>
-<sect2>
+ <sect2>
+ <title>Changes</title>
-<para>
-<programlisting>
Bug Fixes
---------
Fix problems with pg_dump for inheritance, sequences, archive tables(Bruce)
</para>
</sect2>
-<sect2>
+ <sect2>
+ <title>Changes</title>
-<para>
-<programlisting>
-Changes
--------
+ <para>
+ <programlisting>
fix for SET with options (Thomas)
allow pg_dump/pg_dumpall to preserve ownership of all tables/objects(Bruce)
new psql \connect option allows changing usernames without changing databases
Fix for Solaris assembler and include files(Yoshihiko Ichikawa)
allow underscores in usernames(Bruce)
pg_dumpall now returns proper status, portability fix(Bruce)
-</programlisting>
-</para>
-</sect2>
-</sect1>
+ </programlisting>
+ </para>
+ </sect2>
+ </sect1>
<sect1>
<title>Release 6.1</title>
</para>
</sect2>
-<sect2>
+ <sect2>
+ <title>Changes</title>
-<para>
-<programlisting>
Bug Fixes
---------
packet length checking in library routines
</para>
</sect2>
-<sect2>
+ <sect2>
+ <title>Changes</title>
-<para>
-<programlisting>
Bug Fixes
---------
ALTER TABLE bug - running postgress process needs to re-read table definition
<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/sql.sgml,v 1.9 2000/05/02 20:01:52 thomas Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/sql.sgml,v 1.9.2.1 2000/06/14 13:18:59 thomas Exp $
-->
<chapter id="sql">
<example>
<title id="supplier-fig">The Suppliers and Parts Database</title>
<programlisting>
- SUPPLIER SNO | SNAME | CITY SELLS SNO | PNO
- -----+---------+-------- -----+-----
- 1 | Smith | London 1 | 1
- 2 | Jones | Paris 1 | 2
- 3 | Adams | Vienna 2 | 4
- 4 | Blake | Rome 3 | 1
- 3 | 3
- 4 | 2
- PART PNO | PNAME | PRICE 4 | 3
- -----+---------+--------- 4 | 4
- 1 | Screw | 10
- 2 | Nut | 8
- 3 | Bolt | 15
- 4 | Cam | 25
+SUPPLIER: SELLS:
+ SNO | SNAME | CITY SNO | PNO
+----+---------+-------- -----+-----
+ 1 | Smith | London 1 | 1
+ 2 | Jones | Paris 1 | 2
+ 3 | Adams | Vienna 2 | 4
+ 4 | Blake | Rome 3 | 1
+ 3 | 3
+ 4 | 2
+PART: 4 | 3
+ PNO | PNAME | PRICE 4 | 4
+----+---------+---------
+ 1 | Screw | 10
+ 2 | Nut | 8
+ 3 | Bolt | 15
+ 4 | Cam | 25
</programlisting>
</example>
</para>
INTERSECT (∩): builds the set-theoretic intersection of two
tables. Given the tables <classname>R</classname> and
<classname>S</classname>,
- <classname>R</classname> ∪ <classname>S</classname> is the
+ <classname>R</classname> ∩ <classname>S</classname> is the
set of tuples
that are in <classname>R</classname> and in
<classname>S</classname>.
Let the following two tables be given:
<programlisting>
- R A | B | C S C | D | E
- ---+---+--- ---+---+---
- 1 | 2 | 3 3 | a | b
- 4 | 5 | 6 6 | c | d
- 7 | 8 | 9
+R: S:
+ A | B | C C | D | E
+---+---+--- ---+---+---
+ 1 | 2 | 3 3 | a | b
+ 4 | 5 | 6 6 | c | d
+ 7 | 8 | 9
</programlisting>
</para>
</example>
get:
<programlisting>
- R x S A | B | R.C | S.C | D | E
- ---+---+-----+-----+---+---
- 1 | 2 | 3 | 3 | a | b
- 1 | 2 | 3 | 6 | c | d
- 4 | 5 | 6 | 3 | a | b
- 4 | 5 | 6 | 6 | c | d
- 7 | 8 | 9 | 3 | a | b
- 7 | 8 | 9 | 6 | c | d
+R x S:
+ A | B | R.C | S.C | D | E
+---+---+-----+-----+---+---
+ 1 | 2 | 3 | 3 | a | b
+ 1 | 2 | 3 | 6 | c | d
+ 4 | 5 | 6 | 3 | a | b
+ 4 | 5 | 6 | 6 | c | d
+ 7 | 8 | 9 | 3 | a | b
+ 7 | 8 | 9 | 6 | c | d
</programlisting>
</para>
we get:
<programlisting>
- A | B | R.C | S.C | D | E
- ---+---+-----+-----+---+---
- 1 | 2 | 3 | 3 | a | b
- 4 | 5 | 6 | 6 | c | d
+ A | B | R.C | S.C | D | E
+---+---+-----+-----+---+---
+ 1 | 2 | 3 | 3 | a | b
+ 4 | 5 | 6 | 6 | c | d
</programlisting>
</para>
and get:
<programlisting>
- A | B | C | D | E
- ---+---+---+---+---
- 1 | 2 | 3 | a | b
- 4 | 5 | 6 | c | d
+ A | B | C | D | E
+---+---+---+---+---
+ 1 | 2 | 3 | a | b
+ 4 | 5 | 6 | c | d
</programlisting>
</para>
</listitem>
C and D.
Then we define the division as:
-R ÷ S = {t ∣ ∀ t<subscript>s</subscript> ∈ S
- ∃ t<subscript>r</subscript> ∈ R
+ <programlisting>
+R ÷ S = {t ∣ ∀ t<subscript>s</subscript> ∈ S ∃ t<subscript>r</subscript> ∈ R
+ </programlisting>
such that
t<subscript>r</subscript>(A,B)=t∧t<subscript>r</subscript>(C,D)=t<subscript>s</subscript>}
Given the following tables
<programlisting>
- R A | B | C | D S C | D
- ---+---+---+--- ---+---
- a | b | c | d c | d
- a | b | e | f e | f
- b | c | e | f
- e | d | c | d
- e | d | e | f
- a | b | d | e
+R: S:
+ A | B | C | D C | D
+---+---+---+--- ---+---
+ a | b | c | d c | d
+ a | b | e | f e | f
+ b | c | e | f
+ e | d | c | d
+ e | d | e | f
+ a | b | d | e
</programlisting>
R ÷ S
is derived as
<programlisting>
- A | B
- ---+---
- a | b
- e | d
+ A | B
+---+---
+ a | b
+ e | d
</programlisting>
</para>
</listitem>
we will obtain the following result:
<programlisting>
- SNAME
- -------
- Smith
- Adams
+ SNAME
+-------
+ Smith
+ Adams
</programlisting>
</para>
</example>
<para>
The queries used in <acronym>TRC</acronym> are of the following
form:
- x(A) ∣ F(x)
+
+ <programlisting>
+x(A) ∣ F(x)
+ </programlisting>
where <literal>x</literal> is a tuple variable
<classname>A</classname> is a set of attributes and <literal>F</literal> is a
<xref linkend="suppl-rel-alg" endterm="suppl-rel-alg">
using <acronym>TRC</acronym> we formulate the following query:
-<programlisting>
- {x(SNAME) ∣ x ∈ SUPPLIER ∧ \nonumber
- ∃ y ∈ SELLS ∃ z ∈ PART (y(SNO)=x(SNO) ∧ \nonumber
- z(PNO)=y(PNO) ∧ \nonumber
- z(PNAME)='Screw')} \nonumber
+{x(SNAME) ∣ x ∈ SUPPLIER ∧
+ ∃ y ∈ SELLS ∃ z ∈ PART (y(SNO)=x(SNO) ∧
+ z(PNO)=y(PNO) ∧
+ z(PNAME)='Screw')}
</programlisting>
</para>
to involve
arithmetic operations as well as comparisons, e.g.
- A < B + 3.
+ <programlisting>
+A < B + 3.
+ </programlisting>
Note
that + or other arithmetic operators appear neither in relational
used to retrieve data. The syntax is:
<synopsis>
- SELECT [ALL|DISTINCT]
- { * | <replaceable class="parameter">expr_1</replaceable> [AS <replaceable class="parameter">c_alias_1</replaceable>] [, ...
- [, <replaceable class="parameter">expr_k</replaceable> [AS <replaceable class="parameter">c_alias_k</replaceable>]]]}
- FROM <replaceable class="parameter">table_name_1</replaceable> [<replaceable class="parameter">t_alias_1</replaceable>]
- [, ... [, <replaceable class="parameter">table_name_n</replaceable> [<replaceable class="parameter">t_alias_n</replaceable>]]]
- [WHERE <replaceable class="parameter">condition</replaceable>]
- [GROUP BY <replaceable class="parameter">name_of_attr_i</replaceable>
- [,... [, <replaceable class="parameter">name_of_attr_j</replaceable>]] [HAVING <replaceable class="parameter">condition</replaceable>]]
- [{UNION [ALL] | INTERSECT | EXCEPT} SELECT ...]
- [ORDER BY <replaceable class="parameter">name_of_attr_i</replaceable> [ASC|DESC]
- [, ... [, <replaceable class="parameter">name_of_attr_j</replaceable> [ASC|DESC]]]];
+SELECT [ALL|DISTINCT]
+ { * | <replaceable class="parameter">expr_1</replaceable> [AS <replaceable class="parameter">c_alias_1</replaceable>] [, ...
+ [, <replaceable class="parameter">expr_k</replaceable> [AS <replaceable class="parameter">c_alias_k</replaceable>]]]}
+ FROM <replaceable class="parameter">table_name_1</replaceable> [<replaceable class="parameter">t_alias_1</replaceable>]
+ [, ... [, <replaceable class="parameter">table_name_n</replaceable> [<replaceable class="parameter">t_alias_n</replaceable>]]]
+ [WHERE <replaceable class="parameter">condition</replaceable>]
+ [GROUP BY <replaceable class="parameter">name_of_attr_i</replaceable>
+ [,... [, <replaceable class="parameter">name_of_attr_j</replaceable>]] [HAVING <replaceable class="parameter">condition</replaceable>]]
+ [{UNION [ALL] | INTERSECT | EXCEPT} SELECT ...]
+ [ORDER BY <replaceable class="parameter">name_of_attr_i</replaceable> [ASC|DESC]
+ [, ... [, <replaceable class="parameter">name_of_attr_j</replaceable> [ASC|DESC]]]];
</synopsis>
</para>
greater than 10 we formulate the following query:
<programlisting>
- SELECT * FROM PART
- WHERE PRICE > 10;
+SELECT * FROM PART
+ WHERE PRICE > 10;
</programlisting>
and get the table:
<programlisting>
- PNO | PNAME | PRICE
- -----+---------+--------
- 3 | Bolt | 15
- 4 | Cam | 25
+ PNO | PNAME | PRICE
+-----+---------+--------
+ 3 | Bolt | 15
+ 4 | Cam | 25
</programlisting>
</para>
from table PART we use the statement:
<programlisting>
- SELECT PNAME, PRICE
- FROM PART
- WHERE PRICE > 10;
+SELECT PNAME, PRICE
+ FROM PART
+ WHERE PRICE > 10;
</programlisting>
In this case the result is:
using the keywords OR, AND, and NOT:
<programlisting>
- SELECT PNAME, PRICE
- FROM PART
- WHERE PNAME = 'Bolt' AND
+SELECT PNAME, PRICE
+ FROM PART
+ WHERE PNAME = 'Bolt' AND
(PRICE = 0 OR PRICE < 15);
</programlisting>
will lead to the result:
<programlisting>
- PNAME | PRICE
- --------+--------
- Bolt | 15
+ PNAME | PRICE
+--------+--------
+ Bolt | 15
</programlisting>
</para>
take two pieces of a part we could use the following query:
<programlisting>
- SELECT PNAME, PRICE * 2 AS DOUBLE
- FROM PART
- WHERE PRICE * 2 < 50;
+SELECT PNAME, PRICE * 2 AS DOUBLE
+ FROM PART
+ WHERE PRICE * 2 < 50;
</programlisting>
and we get:
<programlisting>
- PNAME | DOUBLE
- --------+---------
- Screw | 20
- Nut | 16
- Bolt | 30
+ PNAME | DOUBLE
+--------+---------
+ Screw | 20
+ Nut | 16
+ Bolt | 30
</programlisting>
Note that the word DOUBLE after the keyword AS is the new title of the
attributes we formulate the following statement:
<programlisting>
- SELECT S.SNAME, P.PNAME
- FROM SUPPLIER S, PART P, SELLS SE
- WHERE S.SNO = SE.SNO AND
- P.PNO = SE.PNO;
+SELECT S.SNAME, P.PNAME
+ FROM SUPPLIER S, PART P, SELLS SE
+ WHERE S.SNO = SE.SNO AND
+ P.PNO = SE.PNO;
</programlisting>
and get the following table as a result:
<programlisting>
- SNAME | PNAME
- -------+-------
- Smith | Screw
- Smith | Nut
- Jones | Cam
- Adams | Screw
- Adams | Bolt
- Blake | Nut
- Blake | Bolt
- Blake | Cam
+ SNAME | PNAME
+-------+-------
+ Smith | Screw
+ Smith | Nut
+ Jones | Cam
+ Adams | Screw
+ Adams | Bolt
+ Blake | Nut
+ Blake | Bolt
+ Blake | Cam
</programlisting>
</para>
the following query:
<programlisting>
- SELECT AVG(PRICE) AS AVG_PRICE
- FROM PART;
+SELECT AVG(PRICE) AS AVG_PRICE
+ FROM PART;
</programlisting>
</para>
The result is:
<programlisting>
- AVG_PRICE
- -----------
- 14.5
+ AVG_PRICE
+-----------
+ 14.5
</programlisting>
</para>
the statement:
<programlisting>
- SELECT COUNT(PNO)
- FROM PART;
+SELECT COUNT(PNO)
+ FROM PART;
</programlisting>
and get:
<programlisting>
- COUNT
- -------
- 4
+ COUNT
+-------
+ 4
</programlisting>
</para>
formulate the query:
<programlisting>
- SELECT S.SNO, S.SNAME, COUNT(SE.PNO)
- FROM SUPPLIER S, SELLS SE
- WHERE S.SNO = SE.SNO
- GROUP BY S.SNO, S.SNAME;
+SELECT S.SNO, S.SNAME, COUNT(SE.PNO)
+ FROM SUPPLIER S, SELLS SE
+ WHERE S.SNO = SE.SNO
+ GROUP BY S.SNO, S.SNAME;
</programlisting>
and get:
<programlisting>
- SNO | SNAME | COUNT
- -----+-------+-------
- 1 | Smith | 2
- 2 | Jones | 1
- 3 | Adams | 2
- 4 | Blake | 3
+ SNO | SNAME | COUNT
+-----+-------+-------
+ 1 | Smith | 2
+ 2 | Jones | 1
+ 3 | Adams | 2
+ 4 | Blake | 3
</programlisting>
</para>
tables SUPPLIER and SELLS is derived:
<programlisting>
- S.SNO | S.SNAME | SE.PNO
- -------+---------+--------
- 1 | Smith | 1
- 1 | Smith | 2
- 2 | Jones | 4
- 3 | Adams | 1
- 3 | Adams | 3
- 4 | Blake | 2
- 4 | Blake | 3
- 4 | Blake | 4
+ S.SNO | S.SNAME | SE.PNO
+-------+---------+--------
+ 1 | Smith | 1
+ 1 | Smith | 2
+ 2 | Jones | 4
+ 3 | Adams | 1
+ 3 | Adams | 3
+ 4 | Blake | 2
+ 4 | Blake | 3
+ 4 | Blake | 4
</programlisting>
</para>
together that agree on both attributes S.SNO and S.SNAME:
<programlisting>
- S.SNO | S.SNAME | SE.PNO
- -------+---------+--------
- 1 | Smith | 1
- | 2
- --------------------------
- 2 | Jones | 4
- --------------------------
- 3 | Adams | 1
- | 3
- --------------------------
- 4 | Blake | 2
- | 3
- | 4
+ S.SNO | S.SNAME | SE.PNO
+-------+---------+--------
+ 1 | Smith | 1
+ | 2
+--------------------------
+ 2 | Jones | 4
+--------------------------
+ 3 | Adams | 1
+ | 3
+--------------------------
+ 4 | Blake | 2
+ | 3
+ | 4
</programlisting>
</para>
query:
<programlisting>
- SELECT S.SNO, S.SNAME, COUNT(SE.PNO)
- FROM SUPPLIER S, SELLS SE
- WHERE S.SNO = SE.SNO
- GROUP BY S.SNO, S.SNAME
- HAVING COUNT(SE.PNO) > 1;
+SELECT S.SNO, S.SNAME, COUNT(SE.PNO)
+ FROM SUPPLIER S, SELLS SE
+ WHERE S.SNO = SE.SNO
+ GROUP BY S.SNO, S.SNAME
+ HAVING COUNT(SE.PNO) > 1;
</programlisting>
and get:
<programlisting>
- SNO | SNAME | COUNT
- -----+-------+-------
- 1 | Smith | 2
- 3 | Adams | 2
- 4 | Blake | 3
+ SNO | SNAME | COUNT
+-----+-------+-------
+ 1 | Smith | 2
+ 3 | Adams | 2
+ 4 | Blake | 3
</programlisting>
</para>
</example>
named 'Screw' we use the query:
<programlisting>
- SELECT *
- FROM PART
- WHERE PRICE > (SELECT PRICE FROM PART
- WHERE PNAME='Screw');
+SELECT *
+ FROM PART
+ WHERE PRICE > (SELECT PRICE FROM PART
+ WHERE PNAME='Screw');
</programlisting>
</para>
The result is:
<programlisting>
- PNO | PNAME | PRICE
- -----+---------+--------
- 3 | Bolt | 15
- 4 | Cam | 25
+ PNO | PNAME | PRICE
+-----+---------+--------
+ 3 | Bolt | 15
+ 4 | Cam | 25
</programlisting>
</para>
greater.
</para>
-<para>
If we want to know all suppliers that do not sell any part
(e.g. to be able to remove these suppliers from the database) we use:
<programlisting>
- SELECT *
- FROM SUPPLIER S
- WHERE NOT EXISTS
- (SELECT * FROM SELLS SE
- WHERE SE.SNO = S.SNO);
+SELECT *
+ FROM SUPPLIER S
+ WHERE NOT EXISTS
+ (SELECT * FROM SELLS SE
+ WHERE SE.SNO = S.SNO);
</programlisting>
</para>
The following query is an example for UNION:
<programlisting>
- SELECT S.SNO, S.SNAME, S.CITY
- FROM SUPPLIER S
- WHERE S.SNAME = 'Jones'
- UNION
- SELECT S.SNO, S.SNAME, S.CITY
- FROM SUPPLIER S
- WHERE S.SNAME = 'Adams';
+SELECT S.SNO, S.SNAME, S.CITY
+ FROM SUPPLIER S
+ WHERE S.SNAME = 'Jones'
+ UNION
+ SELECT S.SNO, S.SNAME, S.CITY
+ FROM SUPPLIER S
+ WHERE S.SNAME = 'Adams';
</programlisting>
gives the result:
<programlisting>
- SNO | SNAME | CITY
- -----+-------+--------
- 2 | Jones | Paris
- 3 | Adams | Vienna
+ SNO | SNAME | CITY
+-----+-------+--------
+ 2 | Jones | Paris
+ 3 | Adams | Vienna
</programlisting>
</para>
Here an example for INTERSECT:
<programlisting>
- SELECT S.SNO, S.SNAME, S.CITY
- FROM SUPPLIER S
- WHERE S.SNO > 1
- INTERSECT
- SELECT S.SNO, S.SNAME, S.CITY
- FROM SUPPLIER S
- WHERE S.SNO > 2;
+SELECT S.SNO, S.SNAME, S.CITY
+ FROM SUPPLIER S
+ WHERE S.SNO > 1
+ INTERSECT
+ SELECT S.SNO, S.SNAME, S.CITY
+ FROM SUPPLIER S
+ WHERE S.SNO > 2;
</programlisting>
gives the result:
<programlisting>
- SNO | SNAME | CITY
- -----+-------+--------
- 2 | Jones | Paris
-The only tuple returned by both parts of the query is the one having $SNO=2$.
+ SNO | SNAME | CITY
+-----+-------+--------
+ 2 | Jones | Paris
</programlisting>
+
+ The only tuple returned by both parts of the query is the one having $SNO=2$.
</para>
<para>
Finally an example for EXCEPT:
<programlisting>
- SELECT S.SNO, S.SNAME, S.CITY
- FROM SUPPLIER S
- WHERE S.SNO > 1
- EXCEPT
- SELECT S.SNO, S.SNAME, S.CITY
- FROM SUPPLIER S
- WHERE S.SNO > 3;
+SELECT S.SNO, S.SNAME, S.CITY
+ FROM SUPPLIER S
+ WHERE S.SNO > 1
+ EXCEPT
+ SELECT S.SNO, S.SNAME, S.CITY
+ FROM SUPPLIER S
+ WHERE S.SNO > 3;
</programlisting>
gives the result:
<programlisting>
- SNO | SNAME | CITY
- -----+-------+--------
- 2 | Jones | Paris
- 3 | Adams | Vienna
+ SNO | SNAME | CITY
+-----+-------+--------
+ 2 | Jones | Paris
+ 3 | Adams | Vienna
</programlisting>
</para>
</example>
one that creates a new relation (a new table). The syntax of the
CREATE TABLE command is:
- <synopsis>
- CREATE TABLE <replaceable class="parameter">table_name</replaceable>
- (<replaceable class="parameter">name_of_attr_1</replaceable> <replaceable class="parameter">type_of_attr_1</replaceable>
- [, <replaceable class="parameter">name_of_attr_2</replaceable> <replaceable class="parameter">type_of_attr_2</replaceable>
- [, ...]]);
+ <synopsis>
+CREATE TABLE <replaceable class="parameter">table_name</replaceable>
+ (<replaceable class="parameter">name_of_attr_1</replaceable> <replaceable class="parameter">type_of_attr_1</replaceable>
+ [, <replaceable class="parameter">name_of_attr_2</replaceable> <replaceable class="parameter">type_of_attr_2</replaceable>
+ [, ...]]);
</synopsis>
<example>
following <acronym>SQL</acronym> statements are used:
<programlisting>
- CREATE TABLE SUPPLIER
- (SNO INTEGER,
- SNAME VARCHAR(20),
- CITY VARCHAR(20));
- </programlisting>
+CREATE TABLE SUPPLIER
+ (SNO INTEGER,
+ SNAME VARCHAR(20),
+ CITY VARCHAR(20));
+ </programlisting>
- <programlisting>
- CREATE TABLE PART
- (PNO INTEGER,
- PNAME VARCHAR(20),
- PRICE DECIMAL(4 , 2));
- </programlisting>
+CREATE TABLE PART
+ (PNO INTEGER,
+ PNAME VARCHAR(20),
+ PRICE DECIMAL(4 , 2));
+ </programlisting>
- <programlisting>
- CREATE TABLE SELLS
- (SNO INTEGER,
- PNO INTEGER);
+CREATE TABLE SELLS
+ (SNO INTEGER,
+ PNO INTEGER);
</programlisting>
</para>
</example>
<replaceable class="parameter">q</replaceable>
of them right to the decimal point.
-(15 ≥ <replaceable class="parameter">p</replaceable> ≥ <replaceable class="parameter">q</replaceable>q ≥ 0).
+(15 ≥ <replaceable class="parameter">p</replaceable> ≥ <replaceable class="parameter">q</replaceable> ≥ 0).
If <replaceable class="parameter">q</replaceable>
is omitted it is assumed to be 0.
the CREATE INDEX command is used. The syntax is:
<programlisting>
- CREATE INDEX <replaceable class="parameter">index_name</replaceable>
- ON <replaceable class="parameter">table_name</replaceable> ( <replaceable class="parameter">name_of_attribute</replaceable> );
+CREATE INDEX <replaceable class="parameter">index_name</replaceable>
+ ON <replaceable class="parameter">table_name</replaceable> ( <replaceable class="parameter">name_of_attribute</replaceable> );
</programlisting>
</para>
we use the following statement:
<programlisting>
- CREATE INDEX I
- ON SUPPLIER (SNAME);
+CREATE INDEX I ON SUPPLIER (SNAME);
</programlisting>
</para>
is:
<programlisting>
- CREATE VIEW <replaceable class="parameter">view_name</replaceable>
- AS <replaceable class="parameter">select_stmt</replaceable>
+CREATE VIEW <replaceable class="parameter">view_name</replaceable>
+ AS <replaceable class="parameter">select_stmt</replaceable>
</programlisting>
where <replaceable class="parameter">select_stmt</replaceable>
<xref linkend="supplier-fig" endterm="supplier-fig"> again):
<programlisting>
- CREATE VIEW London_Suppliers
- AS SELECT S.SNAME, P.PNAME
- FROM SUPPLIER S, PART P, SELLS SE
- WHERE S.SNO = SE.SNO AND
- P.PNO = SE.PNO AND
- S.CITY = 'London';
+CREATE VIEW London_Suppliers
+ AS SELECT S.SNAME, P.PNAME
+ FROM SUPPLIER S, PART P, SELLS SE
+ WHERE S.SNO = SE.SNO AND
+ P.PNO = SE.PNO AND
+ S.CITY = 'London';
</programlisting>
</para>
if it were another base table:
<programlisting>
- SELECT *
- FROM London_Suppliers
- WHERE P.PNAME = 'Screw';
+SELECT * FROM London_Suppliers
+ WHERE P.PNAME = 'Screw';
</programlisting>
which will return the following table:
<programlisting>
- SNAME | PNAME
- -------+-------
- Smith | Screw
+ SNAME | PNAME
+-------+-------
+ Smith | Screw
</programlisting>
</para>
DROP TABLE command is used:
<programlisting>
- DROP TABLE <replaceable class="parameter">table_name</replaceable>;
+DROP TABLE <replaceable class="parameter">table_name</replaceable>;
</programlisting>
</para>
To destroy the SUPPLIER table use the following statement:
<programlisting>
- DROP TABLE SUPPLIER;
+DROP TABLE SUPPLIER;
</programlisting>
</para>
The DROP INDEX command is used to destroy an index:
<programlisting>
- DROP INDEX <replaceable class="parameter">index_name</replaceable>;
+DROP INDEX <replaceable class="parameter">index_name</replaceable>;
</programlisting>
</para>
Finally to destroy a given view use the command DROP VIEW:
<programlisting>
- DROP VIEW <replaceable class="parameter">view_name</replaceable>;
+DROP VIEW <replaceable class="parameter">view_name</replaceable>;
</programlisting>
</para>
</sect3>
The syntax is:
<programlisting>
- INSERT INTO <replaceable class="parameter">table_name</replaceable> (<replaceable class="parameter">name_of_attr_1</replaceable>
- [, <replaceable class="parameter">name_of_attr_2</replaceable> [,...]])
- VALUES (<replaceable class="parameter">val_attr_1</replaceable>
- [, <replaceable class="parameter">val_attr_2</replaceable> [, ...]]);
+INSERT INTO <replaceable class="parameter">table_name</replaceable> (<replaceable class="parameter">name_of_attr_1</replaceable>
+ [, <replaceable class="parameter">name_of_attr_2</replaceable> [,...]])
+ VALUES (<replaceable class="parameter">val_attr_1</replaceable> [, <replaceable class="parameter">val_attr_2</replaceable> [, ...]]);
</programlisting>
</para>
following statement:
<programlisting>
- INSERT INTO SUPPLIER (SNO, SNAME, CITY)
- VALUES (1, 'Smith', 'London');
+INSERT INTO SUPPLIER (SNO, SNAME, CITY)
+ VALUES (1, 'Smith', 'London');
</programlisting>
</para>
To insert the first tuple into the relation SELLS we use:
<programlisting>
- INSERT INTO SELLS (SNO, PNO)
- VALUES (1, 1);
+INSERT INTO SELLS (SNO, PNO)
+ VALUES (1, 1);
</programlisting>
</para>
</sect3>
UPDATE command is used. The syntax is:
<programlisting>
- UPDATE <replaceable class="parameter">table_name</replaceable>
- SET <replaceable class="parameter">name_of_attr_1</replaceable> = <replaceable class="parameter">value_1</replaceable>
- [, ... [, <replaceable class="parameter">name_of_attr_k</replaceable> = <replaceable class="parameter">value_k</replaceable>]]
- WHERE <replaceable class="parameter">condition</replaceable>;
+UPDATE <replaceable class="parameter">table_name</replaceable>
+ SET <replaceable class="parameter">name_of_attr_1</replaceable> = <replaceable class="parameter">value_1</replaceable>
+ [, ... [, <replaceable class="parameter">name_of_attr_k</replaceable> = <replaceable class="parameter">value_k</replaceable>]]
+ WHERE <replaceable class="parameter">condition</replaceable>;
</programlisting>
</para>
relation PART we use:
<programlisting>
- UPDATE PART
- SET PRICE = 15
- WHERE PNAME = 'Screw';
+UPDATE PART
+ SET PRICE = 15
+ WHERE PNAME = 'Screw';
</programlisting>
</para>
FROM. The syntax is:
<programlisting>
- DELETE FROM <replaceable class="parameter">table_name</replaceable>
- WHERE <replaceable class="parameter">condition</replaceable>;
+DELETE FROM <replaceable class="parameter">table_name</replaceable>
+ WHERE <replaceable class="parameter">condition</replaceable>;
</programlisting>
</para>
following statement is used:
<programlisting>
- DELETE FROM SUPPLIER
- WHERE SNAME = 'Smith';
+DELETE FROM SUPPLIER
+ WHERE SNAME = 'Smith';
</programlisting>
</para>
</sect3>
projects / postgresql.git / commitdiff