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

Re: BUG #5783: plpythonu bool behavior change

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5783: plpythonu bool behavior change
Date: 2010-12-05 17:10:06
Message-ID: 1291569006.10677.0.camel@vanquo.pezone.net (view raw or flat)
Thread:
Lists: pgsql-bugs
On sön, 2010-12-05 at 00:25 +0000, Adrian Klaver wrote:
> Seems there was a change in behavior for plpythonu with regards to
> boolean fields from 8.4 to 9.0. Previously, setting a field inside a
> plpythonu function to "f" would work, now that returns a 't' in the
> database field. To get the 'f' to appear I have to specify False
> inside the function.

That change was intentional.


In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2010-12-05 17:26:45
Subject: Re: BUG #5784: CREATE INDEX USING GIN complains about array containing null values yet none exist
Previous:From: Andres FreundDate: 2010-12-05 17:06:20
Subject: Re: BUG #5784: CREATE INDEX USING GIN complains about array containing null values yet none exist

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