Re: [pgsql-sql] Daily digest v1.3328 (5 messages) - Mailing list pgsql-general

From TJ O'Donnell
Subject Re: [pgsql-sql] Daily digest v1.3328 (5 messages)
Date
Msg-id AANLkTi=HSVXiwJDeyc6vvgceZ4mE32cwW8Vn8u4honBh@mail.gmail.com
Whole thread Raw
In response to Re: [pgsql-sql] Daily digest v1.3328 (5 messages)  (Raymond O'Donnell <rod@iol.ie>)
List pgsql-general
Yes indeed, pg_query returns "t" or "f" as strings when selecting
boolean columns.
I was able to switch over to PDO with only an afternoon's work and it works
perfectly for boolean columns, returning values that are properly interpreted
as true and false by php, and by json_encode.  I'm all set now.
Thanks for the help!

TJ O'Donnell

On Thu, Sep 23, 2010 at 1:18 AM, Raymond O'Donnell <rod@iol.ie> wrote:
> On 23/09/2010 02:00, Adrian Klaver wrote:
>>
>> On Wednesday 22 September 2010 5:40:55 pm David Wilson wrote:
>>>
>>> On Wed, Sep 22, 2010 at 8:30 PM, Adrian
>>> Klaver<adrian.klaver@gmail.com>wrote:
>>>>
>>>>  From here;
>>>>
>>>> http://www.postgresql.org/docs/8.4/interactive/datatype-boolean.html
>>>
>>> I believe the question relates to changing the string *output* of the
>>> database to something other than 't' and 'f', not an issue with input
>>> formats.
>>
>> Oops missed that. This would seem to an adapter problem. I work with
>> Python and
>> psycopg2 adapts the boolean values to True and False. Not sure about the
>> PHP
>> solution.
>
> AFAIK the native functions (pg_query() etc) output 't' and 'f', but PDO
> (which I've been using in the context of Zend Framework) output "real" true
> and false values.
>
> Ray.
>
> --
> Raymond O'Donnell :: Galway :: Ireland
> rod@iol.ie
>

pgsql-general by date:

Previous
From: Andrew Hunter
Date:
Subject: Re: Visualize GiST Index
Next
From: Maciek Sakrejda
Date:
Subject: Re: Nested literal parsing rules?