From: Josh Berkus <josh@agliodbs.com>
To: Noel Proffitt <noelp@calpacs.org>
Cc: pgsql-testers@postgresql.org
Subject: Re: Numerics of diffrent scales Raises Type Mismatch Error in a Set Returning Function
Date: Mon, 08 Mar 2010 10:10:03 -0800
Message-ID: <4B953D7B.3020809@agliodbs.com> (raw)
In-Reply-To: <1268030722.6076.131.camel@keg>
References: <1267589227.25740.25.camel@keg>
<1268030722.6076.131.camel@keg>
On 3/7/10 10:45 PM, Noel Proffitt wrote:
> 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.
Please take this up on pgsql-hackers.
--Josh Berkus
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: josh@agliodbs.com, noelp@calpacs.org
Subject: Re: Numerics of diffrent scales Raises Type Mismatch Error in a Set Returning Function
In-Reply-To: <4B953D7B.3020809@agliodbs.com>
References: <1267589227.25740.25.camel@keg> <1268030722.6076.131.camel@keg> <4B953D7B.3020809@agliodbs.com>
* 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