Re: RFC for adding typmods to functions

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: RFC for adding typmods to functions
Date: 2009-11-18 06:56:41
Message-ID: 162867790911172256y5e08b67ey799518eb33ea6836@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>
> So I guess really can't get worked up about the idea of propagating
> this information through the type system.  Even suppose we eventually
> take the steps you suggesting and make it so that varchar(30) ||
> varchar(40) yields varchar(70).  What good is that?

I see main sense in enhancing warning system in plpgsql - or other SQL
PL languages. When you use % reftypes - then there are potential risk
so space (variable, column) isn't well dimensioned.

Pavel

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2009-11-18 07:19:26 Re: RFC for adding typmods to functions
Previous Message Pavel Stehule 2009-11-18 06:11:27 Re: actualised funcs typmod patch