On Sat, 3 Jul 2004, Dario V. Fassi wrote:
> In the sample adjunct, you can see that error arise at the time when the
> view's sql text is parsed and saved in database catalog.
> Then generic NUMERIC type is forced for every calculated column without
> regard or precision.
> And at execute time the f2 column has varying type decimals (in row 2
> you can see 4 decimals and in other rows has 3 decimals), this is not a
> behavior , this is an ERROR.
It isn't clear that an operation like + should retain the same size
restrictions as it's arguments. Consider adding two numeric(6,2) values
of 9999.99, how do you handle the overflow? Your other arguments about the
sizing of derived columns may make sense for your application, but it is
unlikely that they make sense for all users. Note that you can put a cast
into your view definition like so:
CREATER VIEW v AS SELECT (a+b)::numeric(6,2) FROM tab;
Kris Jurka
