David Ciarniello wrote:
>
> I found some bugs working with Access'97-ODBC 7.006 on a Win98 client and
> PostgreSQL 7.1.2 on a Redhat 6.2 server:
>
> 1) subselect side-effects:
> if I run the following query:
>
> select expr1 as field1, expr2 as field2, ... expr-j as field-j, ... expr-n
> as field-n;
> where expr-j is a subselect (e.g. select count(*) from table_x)
>
> I only have results for columns 1 .. j . the driver omits columns j+1 .. n
> (all the columns subsequent the subselect expression)
You seem to turn on *Parse Statements* option setting.
psqlodbc driver doesn't parse compilcated queries well.
OK I will take care of this.
> 2) updating a table without row versioning:
>
> I can't update a table with a float field (but the problem could affect also
> other kind of fields) with row-versioning deactivated.
It's a known issuea and psqlodbc driver isn't guilty.
If row-versioning is activated, appications could use
an optimistic concurrency control using row versions,
otherwise they have to use an optimistic concurrency
control using values.
The main problem is that PostgreSQL servers doesn't
return float values with sufficient precisions.
For example, float4 -> 6, float8 -> 15.
> 3) The driver setting "Use Declare/Fetch" is driver and not datasource
[snip]
> In general I think that making all settings on a per-datasource
> basis would be helpful.
>
Agreed.
I've long wanted to do it but have had no time to do so
unfortunately.
> 4) I can't execute a query like
>
This also seems to be a problem of *Parse Statements*.
I will take care of this too but I'm not sure.
> 5) The odbc connection logfile generated contains the password in a plain
> text format.
> I think this could be a security violation and should be removed.
>
OK I would remove it if there's no objection.
regards,
Hiroshi Inoue