I do understand the cause of the problem. The same holds for different
dialects of SQL.
But I also think it should be a task on the driver side. There should be
a standard.
For the postgresql ODBC driver i think it is a setting in the driver
(booleans as char). But then I can't use the dates.
Please don't make me go from Base through the MS Jet provider to the
postgresql provider.
Ferry
Frank Schönheit - Sun Microsystems Germany wrote:
Hi Ferry,
I did play with that in the past. But hey, why not try again.
Here's the results for Autofilter on a table:
With postgresql over JDBC you need to use the "mixed" mode (that doesn't
sound good, sounds like mixed up).
Using "default" the error is: error boolean = integer (it tries to
compare boolean field "billable" = 1)
Using "SQL"and "Access" the error is: error setting filter criterium (it
tries to compare "Billable" IS TRUE)
Using "Mixed", it works fine. Must have missed that in the passed.
Using Autofilter on a form in Mixed mode also works.
Fine.
The problem here simply is that using a generic bridge (JDBC/ODBC/ADO)
without knowing what backend is accessed, Base doesn't know how to
create the SQL to compare boolean fields, since there is no standard for
this. The option in the advanced setting allows the user to specify
this. (On the long run, I would like to have "profiles", which are
simply a set of configuration entries, which do this. A user would then
simply download such a profile, say named "PostgreSQL via JDBC", install
it, and everything would be fine. But we're not there, yet.)
But using Formfilter on a form (still in mixed mode): Error: operator
does not exist: boolean = integer.
Funny, once the boolean filter is applied using the Autofilter, you can
go to FormFilter and apply additional (non boolean) filters without error.
Issue: 82199
Thanks for submitting this!
Ciao
Frank
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
