From: PG Doc comments form <noreply@postgresql.org>
To: pgsql-docs@lists.postgresql.org
Cc: martin@arp242.net
Subject: Is it wise to include table inheritence in the tutorial?
Date: Sun, 04 Aug 2019 22:14:24 +0000
Message-ID: <156495686451.8638.382610819642178810@wrigleys.postgresql.org> (raw)
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/11/tutorial-inheritance.html
Description:
Hello,
I was reading the tutorial here:
https://www.postgresql.org/docs/11/tutorial-inheritance.html
But on the "don't do this" Wiki, it is strongly advised not to use this:
https://wiki.postgresql.org/wiki/Don't_Do_This#Don.27t_use_table_inheritance
It seems to me that there should at least be a warning, or the entire
section could possible be removed? The tutorial is intended for people new
to PostgreSQL and/or SQL, and introducing features with a large "don't use
this caveat" doesn't strike me as especially helpful?
Cheers,
Martin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: noreply@postgresql.org, pgsql-docs@lists.postgresql.org, martin@arp242.net
Subject: Re: Is it wise to include table inheritence in the tutorial?
In-Reply-To: <156495686451.8638.382610819642178810@wrigleys.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox