Skip site navigation (1) Skip section navigation (2)

Re: UPDATE with data at exec and CURRENT OF question

From: "Hiroshi Saito" <z-saito(at)guitar(dot)ocn(dot)ne(dot)jp>
To: <lothar(dot)behrens(at)lollisoft(dot)de>
Cc: <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: UPDATE with data at exec and CURRENT OF question
Date: 2007-08-16 08:16:34
Message-ID: 054901c7dfdd$c2917eb0$c601a8c0@HP22720319231 (view raw, whole thread or download thread mbox)
Lists: pgsql-odbc

----- Original Message ----- 
From: <lothar(dot)behrens(at)lollisoft(dot)de>

> "Hiroshi Saito" schrieb:
>> Hi.
>> Ah thanks, It is the environment which can reproduce me.
>> Then, I am beginning to make a test code.  There is likely to be a problem
>> of some except for SQL_FETCH_NEXT....
> I have created a small test application only with plain ODBC stuff. I
> could reproduce
> my problem also on Windows with MS SQL Server 2000 !
> You could grab the code here:
> The relevant function is testBlobUpdate.
> On PostgreSQL I did not yet have tested on actual drivers, but when
> the MS SQL driver behaves similar, I suppose still an error in my
> code.
> Regards, Lothar

Uga...Sorry, SQL_CURSOR_KEYSET_DRIVEN cannot be supported yet.:-(
Although I tried it as remembered, it is very difficult correction....
As for the present version, SQL_CURSOR_FORWARD_ONLY and
SQL_CURSOR_STATIC are supported.
To be sure, it needs to exist as TODO.!

Hiroshi Saito 

In response to


pgsql-odbc by date

Next:From: Hiroshi SaitoDate: 2007-08-16 09:29:30
Subject: Re: ODBC driver adding extra characters to table names.
Previous:From: Hiroshi SaitoDate: 2007-08-16 01:24:26
Subject: Re: Psql DBC -08.02.0400 problem, only public schema can be viewed.

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group