Re: BUG #5783: plpythonu bool behavior change - Mailing list pgsql-bugs

From Peter Eisentraut
Subject Re: BUG #5783: plpythonu bool behavior change
Date
Msg-id 1291569006.10677.0.camel@vanquo.pezone.net
Whole thread Raw
In response to BUG #5783: plpythonu bool behavior change  ("Adrian Klaver" <adrian.klaver@gmail.com>)
Responses Re: BUG #5783: plpythonu bool behavior change  (Adrian Klaver <adrian.klaver@gmail.com>)
List 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.

pgsql-bugs by date:

Previous
From: Andres Freund
Date:
Subject: Re: BUG #5784: CREATE INDEX USING GIN complains about array containing null values yet none exist
Next
From: Tom Lane
Date:
Subject: Re: BUG #5784: CREATE INDEX USING GIN complains about array containing null values yet none exist