SEO

#1 (**permalink**) 04-16-2008, 01:37 AM

> -----Original Message-----
> From: pgsql-odbc-owner@postgresql.org
> [mailto

gsql-odbc-owner@postgresql.org] On Behalf Of Ludek Finstrle
> Sent: 05 December 2005 15:17
> To: pgsql-odbc@postgresql.org
> Subject: [ODBC] ODBC driver failure
>
> Hello,
>
> ODBC driver fail (raise exception) with these steps:
> 1) SQLPrepare (SELECT relname FROM pg_class WHERE relname != ?)
> 2) SQLExecute
>
> I found the bug and fix it. Patch is attached.

Thanks Luf, patch applied.

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?

Regards, Dave.

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

#2 (**permalink**) 04-16-2008, 01:37 AM

> 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

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

Re: ODBC driver failure