Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] pgsql: Fix for plpython functions; return true/false for boolean,

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 (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackerspgsql-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

In response to

pgsql-hackers by date

Next:From: David FetterDate: 2007-01-31 17:35:38
Subject: Re: Modifying and solidifying contrib
Previous:From: Andrew DunstanDate: 2007-01-31 14:31:00
Subject: Re: Modifying and solidifying contrib

pgsql-committers by date

Next:From: Teodor SigaevDate: 2007-01-31 15:23:28
Subject: pgsql: Update FreeBSD DocBook installation notices
Previous:From: Teodor SigaevDate: 2007-01-31 15:09:45
Subject: pgsql: Allow GIN's extractQuery method to signal that nothing can

pgsql-patches by date

Next:From: korrydDate: 2007-01-31 16:14:52
Subject: Patch to avoid gprof profiling overwrites
Previous:From: Bruce MomjianDate: 2007-01-31 14:08:38
Subject: Re: [HACKERS] pgsql: Fix for plpython functions; return true/false for boolean,

Privacy Policy | About PostgreSQL
Copyright © 1996-2013 The PostgreSQL Global Development Group