From: Bruce Momjian Date: Tue, 12 Dec 2000 16:47:52 +0000 (+0000) Subject: In 'Joins between classes' in Section 5 of the tutorial we have, in X-Git-Tag: REL7_1_BETA2~187 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=36da236eb313384a8996f2bfd4b51117c34e9344;p=postgresql 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 --- diff --git a/doc/src/sgml/query.sgml b/doc/src/sgml/query.sgml index 32b9b9a2c1..f6c86b930d 100644 --- a/doc/src/sgml/query.sgml +++ b/doc/src/sgml/query.sgml @@ -1,5 +1,5 @@ @@ -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. This is only a conceptual model. The actual join may diff --git a/doc/src/sgml/ref/create_rule.sgml b/doc/src/sgml/ref/create_rule.sgml index 2717037aa8..52b2e9117a 100644 --- a/doc/src/sgml/ref/create_rule.sgml +++ b/doc/src/sgml/ref/create_rule.sgml @@ -1,5 +1,5 @@ @@ -208,14 +208,14 @@ ON UPDATE TO emp-1.salary WHERE emp-2.name = "Joe" CREATE RULE bad_rule_combination_1 AS ON SELECT TO emp DO INSTEAD - SELECT TO toyemp; + SELECT * FROM toyemp; CREATE RULE bad_rule_combination_2 AS ON SELECT TO toyemp DO INSTEAD - SELECT TO emp; + SELECT * FROM emp; This attempt to select from EMP will cause