From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Ludek Finstrle" <luf(at)pzkagis(dot)cz> |
Cc: | <pgsql-odbc(at)postgresql(dot)org> |
Subject: | Re: ODBC driver failure |
Date: | 2005-12-14 14:19:03 |
Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E4E7E98D@ratbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
> -----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
From | Date | Subject | |
---|---|---|---|
Next Message | Ludek Finstrle | 2005-12-14 14:39:20 | Next development steps? |
Previous Message | Ludek Finstrle | 2005-12-14 14:11:15 | Re: ODBC driver failure |