| From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | "Sheng Y(dot) Cheng" <scheng(at)adconion(dot)com>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #5025: Aggregate function with subquery in 8.3 and 8.4. |
| Date: | 2009-09-01 16:39:50 |
| Message-ID: | b42b73150909010939t4a27cae0s934f7b7a0805229e@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tue, Sep 1, 2009 at 4:11 AM, Heikki
Linnakangas<heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
> 2. The semantics of STRICT with row arguments is broken. It should be
> made consistent with IS NULL. Strict function should not be called if
> the argument is a row value with all NULL columns.
not just STRICT, but coalesce(), libpq 'is null' bit, plpgsql row
variables, type input/output, joins, etc. see recent threads on
-hackers and -bugs note that fixing this would break code in the field
(like mine for example) :-).
merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joseph Shraibman | 2009-09-01 16:40:43 | Re: BUG #5028: CASE returns ELSE value always when type is "char" |
| Previous Message | Joseph Shraibman | 2009-09-01 16:36:25 | BUG #5028: CASE returns ELSE value always when type is "char" |