From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Tino Wildenhain <tino(at)wildenhain(dot)de> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Hannu Krosing <hannu(at)skype(dot)net>, Guido Goldstein <guido(dot)goldstein(at)a-nugget(dot)org>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org, pgsql-patches(at)postgresql(dot)org |
Subject: | Re: [HACKERS] pgsql: Fix for plpython functions; return true/false for boolean, |
Date: | 2007-01-31 15:11:13 |
Message-ID: | 25860.1170256273@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers pgsql-patches |
Tino Wildenhain <tino(at)wildenhain(dot)de> writes:
> Bruce Momjian schrieb:
>> I thought about suggesting that, but do we want plpython to have
>> different result behavior based on the version of python used? I didn't
>> think so.
> Why not?
Indeed --- the underlying language changed, so I should think that
python users would *expect* different behavior. +1 on a conditional
patch (see PY_VERSION_HEX...)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Teodor Sigaev | 2007-01-31 15:23:28 | pgsql: Update FreeBSD DocBook installation notices |
Previous Message | Teodor Sigaev | 2007-01-31 15:09:45 | pgsql: Allow GIN's extractQuery method to signal that nothing can |
From | Date | Subject | |
---|---|---|---|
Next Message | David Fetter | 2007-01-31 17:35:38 | Re: Modifying and solidifying contrib |
Previous Message | Andrew Dunstan | 2007-01-31 14:31:00 | Re: Modifying and solidifying contrib |
From | Date | Subject | |
---|---|---|---|
Next Message | korryd | 2007-01-31 16:14:52 | Patch to avoid gprof profiling overwrites |
Previous Message | Bruce Momjian | 2007-01-31 14:08:38 | Re: [HACKERS] pgsql: Fix for plpython functions; return true/false for boolean, |