From: | Richard Huxton <dev(at)archonet(dot)com> |
---|---|
To: | Sim Zacks <sim(at)compulab(dot)co(dot)il> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Access bool integer solution |
Date: | 2005-12-19 09:14:11 |
Message-ID: | 43A679E3.2030703@archonet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Sim Zacks wrote:
> I've been having problems with bools in my Access frontend and
> PostGreSQL backend. The problem is that Access uses -1 for true and 0
> for false and when it does a select it uses those numbers instead of the
> true or false values. PostGreSQL does not have an implicit conversion
> from int to bool, so it was failing was with an error "Operator does not
> exist: boolean=integer"
> I got around this in my queries by using the cbool function, which
> passed in the actual true or false values. This solution did not work
> for internal filters, because it internally calls the select statement
> and does not give an interface to the code.
Are you sure there isn't a setting in the ODBC driver to handle this?
--
Richard Huxton
Archonet Ltd
From | Date | Subject | |
---|---|---|---|
Next Message | Tino Wildenhain | 2005-12-19 09:18:26 | Re: sequences w/o holes |
Previous Message | Tino Wildenhain | 2005-12-19 07:50:48 | Re: sequences in transaction blocks |