Update a couple of example error messages to reflect the fact that we

don't generate constraint names like "$1" anymore.
This commit is contained in:
Tom Lane 2004-08-07 19:53:48 +00:00
parent c71e3de264
commit 82433e913c
2 changed files with 5 additions and 4 deletions

View File

@ -1,5 +1,5 @@
<!-- <!--
$PostgreSQL: pgsql/doc/src/sgml/advanced.sgml,v 1.42 2004/08/01 17:32:11 tgl Exp $ $PostgreSQL: pgsql/doc/src/sgml/advanced.sgml,v 1.43 2004/08/07 19:53:48 tgl Exp $
--> -->
<chapter id="tutorial-advanced"> <chapter id="tutorial-advanced">
@ -123,7 +123,7 @@ INSERT INTO weather VALUES ('Berkeley', 45, 53, 0.0, '1994-11-28');
</programlisting> </programlisting>
<screen> <screen>
ERROR: insert or update on table "weather" violates foreign key constraint "$1" ERROR: insert or update on table "weather" violates foreign key constraint "weather_city_fkey"
DETAIL: Key (city)=(Berkeley) is not present in table "cities". DETAIL: Key (city)=(Berkeley) is not present in table "cities".
</screen> </screen>
</para> </para>
@ -290,6 +290,7 @@ COMMIT;
Remembering the bank database, suppose we debit $100.00 from Alice's Remembering the bank database, suppose we debit $100.00 from Alice's
account, and credit Bob's account, only to find later that we should account, and credit Bob's account, only to find later that we should
have credited Wally's account. We could do it using savepoints like have credited Wally's account. We could do it using savepoints like
this:
<programlisting> <programlisting>
BEGIN; BEGIN;

View File

@ -1,4 +1,4 @@
<!-- $PostgreSQL: pgsql/doc/src/sgml/ddl.sgml,v 1.27 2004/08/03 20:32:30 tgl Exp $ --> <!-- $PostgreSQL: pgsql/doc/src/sgml/ddl.sgml,v 1.28 2004/08/07 19:53:48 tgl Exp $ -->
<chapter id="ddl"> <chapter id="ddl">
<title>Data Definition</title> <title>Data Definition</title>
@ -1971,7 +1971,7 @@ REVOKE CREATE ON SCHEMA public FROM PUBLIC;
<screen> <screen>
DROP TABLE products; DROP TABLE products;
NOTICE: constraint $1 on table orders depends on table products NOTICE: constraint orders_product_no_fkey on table orders depends on table products
ERROR: cannot drop table products because other objects depend on it ERROR: cannot drop table products because other objects depend on it
HINT: Use DROP ... CASCADE to drop the dependent objects too. HINT: Use DROP ... CASCADE to drop the dependent objects too.
</screen> </screen>