The call looks like
SQLRETURN nRetcode = N3SQLForeignKeys(m_aStatementHandle,
(SDB_ODBC_CHAR *) pPKQ, (catalog.hasValue()
&& aPKQ.getLength()) ? SQL_NTS : 0,
(SDB_ODBC_CHAR *) pPKO, pPKO ? SQL_NTS : 0,
(SDB_ODBC_CHAR *) pPKN, pPKN ? SQL_NTS : 0,
(SDB_ODBC_CHAR *) pFKQ, (catalog2.hasValue()
&& aFKQ.getLength()) ? SQL_NTS : 0,
(SDB_ODBC_CHAR *) pFKO, pFKO ? SQL_NTS : 0,
(SDB_ODBC_CHAR *) pFKN, SQL_NTS
);
where the first 3 arguments are NULL. The last 3 contains the
information about one table.
Another way to reproduce the bug would be to install the SRX643C version
of OpenOffice. I just heard from the dev@dba.openoffice.org mailing list
that the snapshot 7.03.0001 shouldn't have the bug anymore.
Best regards,
Ocke
Hiroshi Inoue wrote:
>>-----Original Message-----
>>From: Ocke Janssen
>>
>>Hi all,
>>
>>when using the new PostgreSQL ODBC driver version 7.02.00.05 OpenOffice
>>loops when calling SQLForeignKeys. This doesn't happen when the old
>>driver 7.02.00.3 was used.
>>
>>
>
>Could you send me the example ?
>
>regards,
>Hiroshi Inoue
>
>---------------------------(end of broadcast)---------------------------
>TIP 4: Don't 'kill -9' the postmaster
>
>
--
dba.openoffice.org
Example isn't another way to teach,
it is the only way to teach.
Albert Einstein
