Dave Page wrote:
> 1) ODBC 3 compliance should be checked. Are all the required ODBC
> functions present. Do they work as expected.
A brief status on this: We have all ODBC 3 functions in the code, but
the following functions claim various forms of "not (fully)
Whether any function works as expected is of course undecidable. :-)
> 2) Ditto, Unicode versions of all the functions.
We have almost all the required Unicode functions, but some functions
are in the file odbcapi25w.c, which is not linked in anywhere. What's
up with that? The function GetDescRecW is completely missing.
The additional required SQL functions are also mostly present, but there
seems to be some duplication/overlap between convert.c and odbc.sql,
that isn't quite clear to me yet.
Overall it looks quite good from the conformance point of view.
In response to
pgsql-hackers by date
|Next:||From: Dann Corbit||Date: 2004-07-16 06:38:55|
|Subject: Re: [pgsql-hackers-win32] Weird new time zone |
|Previous:||From: Alvaro Herrera||Date: 2004-07-16 06:13:25|
|Subject: Re: XLogWrite: write request 0/53A4000 is past end of log 0/53A4000|
pgsql-odbc by date
|Next:||From: Dave Page||Date: 2004-07-16 07:17:59|
|Subject: Re: pgODBC and Unicode|
|Previous:||From: lists||Date: 2004-07-16 01:40:24|
|Subject: Re: time columns: ms-access bound controls|