public inbox for [email protected]  

help / color / mirror / Atom feed

From: David Fetter <[email protected]>
To: 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 14:15:05 -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]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

On Fri, Jul 23, 2004 at 04:58:55PM -0400, Tom Lane wrote:
> David Fetter <[email protected]> writes:
> > On Fri, Jul 23, 2004 at 04:30:40PM -0400, Tom Lane wrote:
> >> If we're going to remove from the tutorial every feature for
> >> which any aspect is deemed by someone to be broken, the tutorial
> >> is liable to become quite short.
> 
> > Are there other pieces that are broken?
> 
> Between the locale behavior and the trailing-spaces behavior, one
> could make the case that the entire set of textual datatypes are
> broken.  Other examples will occur to your thought if you follow
> pgsql-bugs.
> 
> My point here is that one man's unusably broken feature may be
> another man's quite useful feature.  Postgres is a work in progress,
> and probably always will be.  I don't object to pointing out
> shortcomings, but removing all mention of a feature because it has
> some shortcomings seems not the best way.

Fair enough.  How about adding an explanation of the limits of table
inheritance illustrated by that example (or other suitable one)?

Cheers,
D
-- 
David Fetter [email protected] http://fetter.org/
phone: +1 510 893 6100   mobile: +1 415 235 3778

Remember to vote!

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