Re: Improving ALTER TYPE support

Makes more sense to do that, and I think it'll be cleaner to implement as
well.

On 5/23/06, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
>
> John,
>
> > I've been working on a function which returns a setof a composite type.
> > Everytime I've changed the structure of the returning setof, I've had to
> > change the type accordingly, which current means doing a drop type ...
> > cascade down to the function. We should allow one of the following:
>
> Why not go all the way and work out a way to define an SRF return type as
> a
> part of the function? e.g.
>
> CREATE OR REPLACE FUNCTION some_srf ( param1 int, param2 text )
> RETURNS some_srf ( col1 int, col2 numeric ) AS ....
>
> Then the "replace" function would automatically rebuild the type.
>
> --
> Josh Berkus
> PostgreSQL @ Sun
> San Francisco
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
> choose an index scan if your joining column's datatypes do not
> match
>