From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | Noel Proffitt <noelp(at)calpacs(dot)org> |
Cc: | pgsql-testers(at)postgresql(dot)org |
Subject: | Re: Numerics of diffrent scales Raises Type Mismatch Error in a Set Returning Function |
Date: | 2010-03-08 18:10:03 |
Message-ID: | 4B953D7B.3020809@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-testers |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Chander Ganesan | 2010-03-11 13:19:53 | Documentation/Cleanup Command for Hot Standby |
Previous Message | Noel Proffitt | 2010-03-08 06:45:22 | Re: Numerics of diffrent scales Raises Type Mismatch Error in a Set Returning Function |