Re: UPDATE with data at exec and CURRENT OF question
От | Hiroshi Saito |
---|---|
Тема | Re: UPDATE with data at exec and CURRENT OF question |
Дата | |
Msg-id | 054901c7dfdd$c2917eb0$c601a8c0@HP22720319231 обсуждение исходный текст |
Ответ на | UPDATE with data at exec and CURRENT OF question ("lothar.behrens@lollisoft.de" <lothar.behrens@lollisoft.de>) |
Ответы |
Re: UPDATE with data at exec and CURRENT OF question
|
Список | pgsql-odbc |
Hi. ----- Original Message ----- From: <lothar.behrens@lollisoft.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: > > http://lbdmf.cvs.sourceforge.net/lbdmf/CPP/RegressionTests/Database/Plain-ODBC-Test-Blob/test.cpp?revision=1.4&view=markup > > 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.! Regards, Hiroshi Saito
В списке pgsql-odbc по дате отправления: