mirror of
https://github.com/postgres/postgres.git
synced 2025-07-30 11:03:19 +03:00
In 'Joins between classes' in Section 5 of the tutorial we have, in
the first paragraph: As an example, say we wish to find all the records that are in the temperature range of other records. In effect, we need to compare the temp_lo and temp_hi attributes of each EMP instance to the temp_lo and temp_hi attributes of all other EMP instances. I believe that EMP should read WEATHER, as the example query that follows joins WEATHER to itself. EMP is often used in Oracle examples. Regards, Graham Other RULE cleanups
This commit is contained in:
@ -1,5 +1,5 @@
|
||||
<!--
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/query.sgml,v 1.13 2000/09/29 20:21:34 petere Exp $
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/query.sgml,v 1.14 2000/12/12 16:47:52 momjian Exp $
|
||||
-->
|
||||
|
||||
<chapter id="query">
|
||||
@ -273,8 +273,8 @@ SELECT * INTO TABLE temp FROM weather;
|
||||
As an example, say we wish to find all the records that
|
||||
are in the temperature range of other records. In
|
||||
effect, we need to compare the temp_lo and temp_hi
|
||||
attributes of each EMP instance to the temp_lo and
|
||||
temp_hi attributes of all other EMP instances.
|
||||
attributes of each WEATHER instance to the temp_lo and
|
||||
temp_hi attributes of all other WEATHER instances.
|
||||
<note>
|
||||
<para>
|
||||
This is only a conceptual model. The actual join may
|
||||
|
Reference in New Issue
Block a user