SEO

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

> -----Original Message-----
> From: Ludek Finstrle [mailto:luf@pzkagis.cz]
> Sent: 05 December 2005 17:01
> To: Dave Page
> Cc: pgsql-odbc@postgresql.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.

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

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

> > I think psqlodbc-server_side_prepare.diff and
>
> Which ones that one? - I lost track :-(

This is included in psqlodbc-08.01.0102.

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

Do you mean diff or sequence of steps?

> time to investigate further please?

I have a lot of other work. Maybe later.
There is problem with bytea, Autocommit and Cancel, ColAttribure (maybe
this is problem of VB6 RowCount).
When there is no one report it. I didn't investigate it in near future.
And there is question of cleaning old unused code.

Luf

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

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

On 5/12/05 6:06 pm, "Ludek Finstrle" <luf@pzkagis.cz> wrote:

>>> I think psqlodbc-server_side_prepare.diff and
>>
>> Which ones that one? - I lost track :-(
>
> This is included in psqlodbc-08.01.0102.

Ah that one- thanks.

>>> psqlodbc_server_side_prepare2.diff are good enough. But I'm waiting if
>>> Rainer send steps which leads to bug.
>>
>> Got that one.
>
> Do you mean diff or sequence of steps?

Diff. I'll apply it tomorrow.

>> time to investigate further please?
>
> I have a lot of other work. Maybe later.
> There is problem with bytea, Autocommit and Cancel, ColAttribure (maybe
> this is problem of VB6 RowCount).
> When there is no one report it. I didn't investigate it in near future.
> And there is question of cleaning old unused code.

Yeah. We'll get there in the end!!!

Regards, Dave

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

#4 (**permalink**) 04-16-2008, 01:39 AM

> > 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 ;-)

Luf

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

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