bug in documentation

From: Caspar Bothmer <caspar(at)cbothmer(dot)org>
To: pgsql-bugs(at)postgresql(dot)org
Subject: bug in documentation
Date: 2002-05-26 09:37:33
Message-ID: 3CF0ACDD.1CDBF3EA@cbothmer.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

My name: Caspar
Email: caspar(at)cbothmer(dot)org

Description in Documentation:

the 7.2-tutorials available online, both formats (US and A4) at

http://www.de.postgresql.org/users-lounge/docs/7.2/tutorial-7.2-A4.pdf

respectively

http://www.de.postgresql.org/users-lounge/docs/7.2/tutorial-7.2-US.pdf

have this error at chapter 3.3 (foreign keys):

in

CREATE TABLE weather (

it reads

city varchar(80) references weather,

but it should be

city varchar(80) references cities,

Postgresql creates an

ERROR: PRIMARY KEY for referenced table "weather" not found

so the only affect will be that someone trying it out would have to
think about this problem. The error is an obvious one, I read through
the docs and was sure that this wouldn't be ok and just tried it out
myself to verify my first impression.

There is an error message given with the INSERT example right there but
it is trunkated ("not foun") so one can't see whether is reads "not
found in weather" or "not found in cities". If your source says weather
I would recommend changing it there as well.

bye

caspar

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2002-05-26 16:20:24 Re: bug in documentation
Previous Message Tom Lane 2002-05-26 03:25:04 Re: Bug #676: lower(), upper(), & initcap() do not work on utf-8 chars