Re: sugsestions - Mailing list pgsql-hackers

From ivan
Subject Re: sugsestions
Date
Msg-id Pine.LNX.4.56.0307102056340.25199@rex.anfa.pl
Whole thread Raw
In response to Re: sugsestions  (Rod Taylor <rbt@rbt.ca>)
List pgsql-hackers

On Wed, 9 Jul 2003, Rod Taylor wrote:

> On Tue, 2003-07-08 at 21:31, ivan wrote:
> > What do you think about :
> >
> > 1. OPTION RETURNS NULL ON NULL INPUT (when function is created) change to
> >   RETURNS <val> ON NULL INPUT .... ???
>
> I personally think this should be up to the specific function to
> capture.  This way it could be a complex result.
>
> > 2. CREATE TYPE .. with  INHERITS (..) like in CREATE TABLE
> >  but type should be normaly with including base type
> >  create type A AS (A INT,B INT);
> > and
> >  create type B AS (C INT, D INT) INHERITS( A ); ==
> >  create type B AS (A INT, B INT, C INT, D INT );
> >  can be ??
>
> I like this.  The equivalent table syntax for absorbing table structure
> into another table is LIKE:
>
> CREATE TABLE othertable (acol integer);
> CREATE TABLE a (col integer, LIKE othertable, anothercol integer);
>
> I could see:
>
> CREATE TYPE a AS (a integer, b integer);
> CREATE TYPE b AS (LIKE a, c integer, d integer);
>

This way is very good !!
I see i thing :

CREATE TABLE a AS (a int, b int);
CREATE TABLE b AS (x a.a%ROWTYPE, a int, b a.b%ROWTYPE);
like in plpgsql...
May be there should be others word , but i want to show my view .. :>


pgsql-hackers by date:

Previous
From: Rod Taylor
Date:
Subject: Re: static dumper idea
Next
From: "Jenny -"
Date:
Subject: table-level and row-level locks.