Re: ODBC driver failure
От | Ludek Finstrle |
---|---|
Тема | Re: ODBC driver failure |
Дата | |
Msg-id | 20051205170040.GA16687@soptik.pzkagis.cz обсуждение исходный текст |
Ответ на | Re: ODBC driver failure ("Dave Page" <dpage@vale-housing.co.uk>) |
Список | pgsql-odbc |
> BTW, did I understand from your earlier email that you are still looking > at the other server side prepare issue we've been discussing with > Rainer, or is the last patch good in your opinion? I think psqlodbc-server_side_prepare.diff and psqlodbc_server_side_prepare2.diff are good enough. But I'm waiting if Rainer send steps which leads to bug. BTW do you know why ExecDirect test open cursor? I'm talking about SELECT statements. Cursor is opened in PGAPI_Execute so there can't be called ExecDirect after Execute or ExecDirect. There is no limitation for calling Execute, Prepare, Execute :-( Check in SQLDirect is done by SC_opencheck: if (res = SC_get_Curres(self), NULL != res) { if (res->backend_tuples) { SC_set_error(self, STMT_SEQUENCE_ERROR, "The cursor is open."); SC_log_error(func, "", self); return TRUE; } } I have no idea why is it doing this way :-( Luf
В списке pgsql-odbc по дате отправления: