Received: from me.tm.ee (ppp130.tele2.ee [212.107.33.130])
	by hub.org (8.9.3/8.9.3) with ESMTP id PAA13568
	for <pgsql-hackers@postgresql.org>;
	Sun, 21 May 2000 15:45:15 -0400 (EDT) (envelope-from hannu@tm.ee)
Received: from tm.ee (IDENT:hannu@localhost.localdomain [127.0.0.1])
	by me.tm.ee (8.9.3/8.9.3) with ESMTP id VAA00887;
	Sun, 21 May 2000 21:42:03 +0300
Message-ID: <39282DFB.C2A6EE84@tm.ee>
Date: Sun, 21 May 2000 21:42:03 +0300
From: Hannu Krosing <hannu@tm.ee>
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.12-20 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Chris <chris@bitmead.com>
CC: Peter Eisentraut <peter_e@gmx.net>,
	PostgreSQL Development <pgsql-hackers@postgresql.org>
Subject: Re: Thus spoke SQL3 (on OO)
References: <Pine.LNX.4.21.0005201507330.423-100000@localhost.localdomain>
	<39273BAD.CA8F3AF5@bitmead.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Archive-Number: 200005/394

Chris wrote:
> 
> 
> > What exactly IDENTITY is is still a bit unclear to me but it is
> > definitely not the proposed identification of the table a row came
> > from.
> 
> How do you know?
> 
> > * Cloning
> > CREATE TABLE name (
> >     colname type,
> >     colname type,
> >     LIKE other_table,
> >     colname type,
> >     ...
> > );
> 
> Hmm. Fairly useless feature IMO.

The main use would be for those users who are using INHERITS with
current
PostgreSQL and need to port from it.

---------
Hannu