From: | "Inoue, Hiroshi" <h-inoue(at)dream(dot)email(dot)ne(dot)jp> |
---|---|
To: | "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com> |
Cc: | "pgsql-odbc(at)postgresql(dot)org" <pgsql-odbc(at)postgresql(dot)org> |
Subject: | Re: Some bug fixes and improvements |
Date: | 2016-03-30 08:31:50 |
Message-ID: | 56FB8EF6.3010301@dream.email.ne.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
井上です。
On 2016/03/29 11:17, Tsunakawa, Takayuki wrote:
> Hello, Inoue-san and all,
>
> While I'm learning the psqlODBC source code and investigating the cause of the scroll cursor crash problem I reported in January, I found some bugs and useless code fragments. Please find the attached patches to remove them. I hope these will be included in the next release.
ありがとうございます。
ineffective_code.patchとwin_build.patchを除いてpushしました。
ineffective_code.patchは関しては、なぜCC_on_abort_partialが抜けてしまっ
たのか調べる必要がありま す。 これはsavepoint単位のrollback時に必要な処
理をするものです。
win_build.patchに関しては、使用を勧めてはいないnmake関連のバグを修正する
というのは矛盾を感じるというか何というか。
>
> However, I've not been able to find the cause of the crash. The code of psqlODBC is pretty complex, particularly around handling cursors, isn't it?
とりあえず、 crashについて基本的なことを確認させてください。
declare/fetchモードですか?
以前のメールにあったトレースの中で
psqlodbc35w.dll!SQLFetchScroll(void * StatementHandle=0x007f3b30,
short FetchOrientation=5, long FetchOffset=27326472)
の引数(FetchOrientation=SQL_FETCH_ABSOLUTEとFetchOffset)は正しいと
考えてよろしいので しょうか?
From | Date | Subject | |
---|---|---|---|
Next Message | Bill Kuhn | 2016-03-30 19:00:01 | 10 row/second insert in ssis |
Previous Message | Fernando Luna | 2016-03-29 15:33:27 | Re: Question regarding accessing only tables to which the user has access |