pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Hannu Krosing <hannu@tm.ee>
To: chris@bitmead.com
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Mark Hollomon <mhh@nortelnetworks.com>
Cc: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: pgsql-hackers@postgreSQL.org
Cc: pgsql-sql@postgreSQL.org
Subject: Re: [HACKERS] Re: [SQL] Proposed Changes to PostgreSQL
Date: Sat, 05 Feb 2000 00:37:35 +0200
Message-ID: <389B54AF.9614B3D3@tm.ee> (raw)
References: <200002030402.XAA03844@candle.pha.pa.us>
	<38998548.C6C8606A@americasm01.nt.com>
	<28272.949596778@sss.pgh.pa.us>
	<389A157B.1EDF669@nimrod.itg.telecom.com.au>

Chris Bitmead wrote:
> 
> Tom, I agree with most of what you say. If we want to have ** be the
> default
> syntax for getting sub-columns I can live with that (for suggestion (3))
> 
> But for (2), I do feel very strongly that getting sub-tuples should be
> the
> "default default", and a SET GETSUBCLASSES=true should be the default
> setting.

Then maybe we need a way to "break off" inheritance, i.e. make the inherited 
table independent but retain the columns as they are at the time of breakage.

At least it could be given as an option in pg_dump. (--dump_flat_creates or
smth.)

> I've been using the postgres inheritance for a real system and I can
> say with certainty that this is a massive source of errors. Not
> wanting sub-class tuples seems rarely needed, and leaving off the "*" is
> something that too often seems forgotten. I often can trawl through
> code and realise that some query is missing the "*" but it hasn't been
> discovered yet. In fact I find that almost all queries require the "*"
> when you have a proper OO model, and not using "*" is usually laziness.

True. I also think that people who used inheritance as a create table shortcut
can most easily ensure compatibility by dumping their not-really-inherited 
tables as independent. They will have to dump-relaod anyway.

> Also when adding a sub-class where there previously was none, one
> usually has to trawl through the queries and add "*" to all of them
> because as I said, there are almost never occasions where "*" is not
> required in real life OO models.
> 
> So I understand the compatibility issue here, but I really feel strongly
> that this should be changed now before there really are a lot of people
> using it. Sure, have as many compatibility modes as you like, but I
> think
> this is a broken enough design that the default should be changed.
> Apparently Illustra/Informix agreed.

And they are probably the only external DB we can aim to be compatible with,
or what does SQL3 say?

----------------------
Hannu



view thread (68+ messages)  latest in thread

Message-ID: <389B54AF.9614B3D3@tm.ee>
Permalink:  ../389B54AF.9614B3D3@tm.ee/
Also on:    postgresql.org/message-id/389B54AF.9614B3D3@tm.ee

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-sql@postgresql.org
  Cc: hannu@tm.ee, chris@bitmead.com, tgl@sss.pgh.pa.us, mhh@nortelnetworks.com, pgman@candle.pha.pa.us, pgsql-hackers@postgreSQL.org
  Subject: Re: [HACKERS] Re: [SQL] Proposed Changes to PostgreSQL
  In-Reply-To: <389B54AF.9614B3D3@tm.ee>
  References: <200002030402.XAA03844@candle.pha.pa.us> <38998548.C6C8606A@americasm01.nt.com> <28272.949596778@sss.pgh.pa.us> <389A157B.1EDF669@nimrod.itg.telecom.com.au> <389B54AF.9614B3D3@tm.ee>

* 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