| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Joe Conway <mail(at)joeconway(dot)com> |
| Cc: | "Hackers (PostgreSQL)" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: odd behavior/possible bug |
| Date: | 2003-07-24 21:13:33 |
| Message-ID: | 19356.1059081213@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Joe Conway <mail(at)joeconway(dot)com> writes:
> Tom Lane wrote:
>> We could probably hack the inlining logic to prevent it from inlining
>> the function in this scenario, but I wonder whether this doesn't say
>> that ExecEvalArray is behaving inconsistently. In other operations, any
>> NULL in means NULL out. Shouldn't it simply quietly return a NULL array
>> if one of the supplied elements is NULL?
> That probably makes good sense, at least until we can deal with NULL
> elements. Would that patch count as a bug fix?
Either one would count as a bug fix IMHO. Anyone else have an opinion
on which to do?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marcus Brger | 2003-07-24 21:17:01 | Re: php with postgres |
| Previous Message | Bruce Momjian | 2003-07-24 21:05:21 | Re: php with postgres |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephan Szabo | 2003-07-24 21:28:27 | Re: odd behavior/possible bug |
| Previous Message | Joe Conway | 2003-07-24 20:47:59 | Re: odd behavior/possible bug |