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
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 Klaverwrote:
From here;
http://www.postgresql.org/docs/8.4/interactive/datatype-boolean.html
I believe the question relates to changing the string
On Wednesday 22 September 2010 5:40:55 pm David Wilson wrote:
> On Wed, Sep 22, 2010 at 8:30 PM, Adrian Klaver 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 s
On Wed, Sep 22, 2010 at 8:30 PM, Adrian Klaver 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.
On Wednesday 22 September 2010 5:12:45 pm TJ O'Donnell wrote:
> Many frameworks do not natively recognize "t" as true and "f" as false.
> I'm using php, json_encode and extjs.
> Is it possible to cause the default output of boolean values to be
> something other than "t" and "f", say "true" and "fa
Many frameworks do not natively recognize "t" as true and "f" as false.
I'm using php, json_encode and extjs.
Is it possible to cause the default output of boolean values to be something
other than "t" and "f", say "true" and "false" or even 1 and 0?
Of course I can do this for an individual query
