From: Noel Proffitt <noelp@calpacs.org>
To: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-testers@postgresql.org
Subject: Re: Numerics of diffrent scales Raises Type Mismatch Error in a Set Returning Function
Date: Sun, 7 Mar 2010 22:45:22 -0800
Message-ID: <1268030722.6076.131.camel@keg> (raw)
In-Reply-To: <4B94320B.9000804@agliodbs.com>
References: <1267589227.25740.25.camel@keg>
On Sun, 2010-03-07 at 15:08 -0800, Josh Berkus wrote:
> Per pgsql-bugs, it's an expected compatibility issue due to unifying the
> SQL and PLPGSQL parsers. That is, the fact that plpgsql used to let you
> do this was regarded as a bug, and was not consistent with the SQL
> command line.
>
> Worth noting in the release notes as part of a general class of
> backwards-compatibility issues.
>
> --Josh Berkus
>
Note that this behavior change affects seems to affect other types who's
size is different such as character varying.
I'm probably not understanding, but I'm not sure I follow what the
consistency issue is. It seems like in most other parts of PG, types are
cast sensibly without complaint.
In 9.0 and 8.4 we can do things like:
CREATE TABLE foo (n NUMERIC(10,2));
INSERT INTO foo values (42.777777::NUMERIC(12,2));
INSERT INTO foo values (42.777777::NUMERIC(8,2));
INSERT INTO foo values (42.777777::NUMERIC(14,8));
SELECT * FROM foo
JOIN (VALUES (42.78::NUMERIC)) AS bar(m) ON foo.n = bar.m;
The values are rounded and cast; Same with varchar of various sizes.
But when returning a setof things are now strictly checked. However,
when selecting into a record PL doesn't complain if the sizes don't
match the substructure. Also curious is that single value return types
are not too particular. For example:
CREATE OR REPLACE FUNCTION check_me() RETURNS VARCHAR(2) AS
$$
BEGIN
RETURN 42.7777::NUMERIC(7,4);
END;
$$ LANGUAGE 'plpgsql';
SELECT *,pg_typeof(check_me) FROM check_me();
check_me | pg_typeof
----------+-------------------
42.7777 | character varying
(1 row)
-Noel Proffitt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-testers@postgresql.org
Cc: noelp@calpacs.org, josh@agliodbs.com
Subject: Re: Numerics of diffrent scales Raises Type Mismatch Error in a Set Returning Function
In-Reply-To: <1268030722.6076.131.camel@keg>
References: <1267589227.25740.25.camel@keg> <1268030722.6076.131.camel@keg>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox