Re: ODBC driver failure

> -----Original Message-----
> From: Ludek Finstrle [mailto:luf(at)pzkagis(dot)cz]
> Sent: 05 December 2005 17:01
> To: Dave Page
> Cc: pgsql-odbc(at)postgresql(dot)org
> Subject: Re: [ODBC] ODBC driver failure
>
> > 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

Which ones that one? - I lost track :-(

> psqlodbc_server_side_prepare2.diff are good enough. But I'm waiting if
> Rainer send steps which leads to bug.

Got that one.

> 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 :-(

No, nor do I offhand. I'm really busy at the moment though - do you have
time to investigate further please?

Thanks, Dave.