Re: ODBC driver failure

> -----Original Message-----
> From: Ludek Finstrle [mailto:luf(at)pzkagis(dot)cz]
> Sent: 14 December 2005 14:11
> To: Dave Page
> Cc: pgsql-odbc(at)postgresql(dot)org
> Subject: Re: [ODBC] ODBC driver failure
>
> > > 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?
>
> I'm studying ODBC specification and I find answer. psqlODBC
> behaviour is
> right. The app have to close cursor prior to Execute new query.
> So this is done ;-)

:-)

/D