pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: martin@arp242.net
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: Is it wise to include table inheritence in the tutorial?
Date: Mon, 05 Aug 2019 10:17:40 -0400
Message-ID: <12462.1565014660@sss.pgh.pa.us> (raw)
In-Reply-To: <156495686451.8638.382610819642178810@wrigleys.postgresql.org>
References: <156495686451.8638.382610819642178810@wrigleys.postgresql.org>

PG Doc comments form <noreply@postgresql.org> writes:
> 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

That wiki entry is just some random person's opinion, it's not
project policy.

Having said that, the partitioning feature is approaching the
point of being mature enough to recommend to novices, so maybe
we should start thinking about adjusting the tutorial with that
in mind.  I wouldn't necessarily remove the inheritance section;
it's talking about OOP-style inheritance, which you can't get
with partitioning.

			regards, tom lane





view thread (3+ messages)  latest in thread

Message-ID: <12462.1565014660@sss.pgh.pa.us>
Permalink:  ../12462.1565014660@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/12462.1565014660@sss.pgh.pa.us

 · 

reply

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: tgl@sss.pgh.pa.us, martin@arp242.net, pgsql-docs@lists.postgresql.org
  Subject: Re: Is it wise to include table inheritence in the tutorial?
  In-Reply-To: <12462.1565014660@sss.pgh.pa.us>

* 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