public inbox for [email protected]  

help / color / mirror / Atom feed

From: elein <[email protected]>
To: David Fetter <[email protected]>
Cc: Tom Lane <[email protected]>
Cc: Peter Eisentraut <[email protected]>
Cc: Robert Treat <[email protected]>
Cc: Joe Conway <[email protected]>
Cc: elein <[email protected]>
Cc: [email protected]
Subject: Re: [HACKERS] Tutorial
Date: Fri, 23 Jul 2004 13:25:56 -0700
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

Perhaps after OSCON I can work with fetter on getting
the documentation clarified.  OK?

--elein

On Fri, Jul 23, 2004 at 12:34:13PM -0700, David Fetter wrote:
> On Fri, Jul 23, 2004 at 03:31:47PM -0400, Tom Lane wrote:
> > David Fetter <[email protected]> writes:
> > > What *is* broken is table inheritance, and the docs need to reflect
> > > this.
> > 
> > The combination of inheritance with certain other features is broken,
> > yes, and the docs do reflect that (see the bottom of 
> > http://www.postgresql.org/docs/7.4/static/ddl-inherit.html
> > for example).
> > 
> > I will grant you that this page is a near duplicate of the
> > tutorial's discussion of inheritance, which is surely bad --- either
> > they should be exact duplicates, or one or the other needs
> > rewriting.  But I'm not really going to hold still for the docs on
> > inheritance being rewritten by someone who considers the entire
> > concept broken.  Maybe we can get elein to do it ;-)
> 
> I don't consider the concept broken.  The implementation is, in fact,
> broken, and putting that broken piece in the tutorial is, imnsho, a
> bad mistake.
> 
> Cheers,
> D
> -- 
> David Fetter [email protected] http://fetter.org/
> phone: +1 510 893 6100   mobile: +1 415 235 3778
> 
> Remember to vote!
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster

view thread (19+ messages)  latest in thread

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: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: [HACKERS] Tutorial
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox