## Various doc errors and shortcomings

From: Charles Obler pgsql-bugs(at)postgresql(dot)org Various doc errors and shortcomings 2001-08-15 18:28:53 3B7ABF65.3A430AC3@hovac.com (view raw or flat) 2001-08-15 18:28:53 from Charles Obler  2001-08-20 15:53:39 from Peter Eisentraut pgsql-bugs
Hello PostgreSQL!

I've found several errors in the documentation.  The first is
a shortcoming rather than an error, but it cost me hours of
needless effort.  You said you welcome bug reports, so here's
what I have:

- - - - -

Programmer's Guide, 8.2.3. Connecting to the Database

According to the documentation, the URL includes what is called
"the database name".  I assumed that the fully qualified path
name was intended here, since that is what normally appears in a
URL.  How else does one unambiguously identify a file?  So that
is what I tried, and it repeatedly resulted in cryptic "no
suitable driver" messages.  I thought the problem was in the
Java configuration.

One or two examples are needed in this section to make it clear
that postgresql has its own directory of "registered" databases,
and the "database name" in question is the name in this
registry, not the database filename.

- - - - -

Tutorial Chapter 2:

In the following "&cup" is erroneously used to represent
intersection:

Relational Algebra

INTERSECT (&cap;): builds the set-theoretic intersection of
two tables. Given the tables R and S, R &cup; S is the set of
tuples that are in R and in S. We again require that R and S
have the same arity.

- - - - -

Tutorial Chapter 2:

What does the "\nonumber" signify in the following?

Tuple Relational Calculus

The queries used in TRC are of the following form: x(A) &mid;
F(x) where x is a tuple variable A is a set of attributes and F
is a formula. The resulting relation consists of all tuples t(A)
that satisfy F(t).

If we want to answer the question from example A Query Using
Relational Algebra using TRC we formulate the following query:

{x(SNAME) &mid; x &isin; SUPPLIER &and; \nonumber
&exist; y &isin; SELLS &exist; z &isin;
PART (y(SNO)=x(SNO) &and; \nonumber
z(PNO)=y(PNO) &and; \nonumber
z(PNAME)='Screw')} \nonumber

Evaluating the query against the tables from The Suppliers and
Parts Database again leads to the same result as in A Query
Using Relational Algebra.

- - - - -

Tutorial Chapter 2:

In the following, the condition should be "PRICE <= 15"

Example 2-4. Simple Query with Qualification

The qualifications in the WHERE clause can also be logically
connected using the keywords OR, AND, and NOT:

SELECT PNAME, PRICE
FROM PART
WHERE PNAME = 'Bolt' AND
(PRICE = 0 OR PRICE < 15);

PNAME  |  PRICE
--------+--------
Bolt   |   15

- - - - -

Tutorial Chapter 2:

The following example seems incorrect.  In S.SNO is greater than
2, then S.SNO is also greater than 1, so the intersection should
include suppliers 2, 3, 4, etc..

Here an example for INTERSECT:

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;

gives the result:

SNO | SNAME |  CITY
-----+-------+--------
2  | Jones | Paris
The only tuple returned by both parts of the query is the one
having $SNO=2$.

- - - - -

### pgsql-bugs by date

 Next: From: Truong, Long Date: 2001-08-16 12:02:53 Subject: openVMS 7.2 Previous: From: Peter Eisentraut Date: 2001-08-15 15:50:14 Subject: Re: -ltermcap needed for psql client build on OpenBSD 2.9