From: | Hiroshi Inoue <inoue(at)tpf(dot)co(dot)jp> |
---|---|
To: | Randy Yates <yates(at)ieee(dot)org> |
Cc: | pgsql-odbc(at)postgresql(dot)org |
Subject: | Re: psqlODBC Unicode 8.01.02.00 Driver "Overflows" On MS-Access |
Date: | 2006-03-17 00:31:05 |
Message-ID: | 441A0349.8050603@tpf.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
Randy Yates wrote:
> inoue(at)tpf(dot)co(dot)jp (Hiroshi Inoue) writes:
>
>
>>Randy Yates wrote:
>>
>>>Tim(dot)Clarke(at)manifest(dot)co(dot)uk ("Tim Clarke") writes:
>>>
>>>
>>>>Whenever I get these I write a tiny "stuff one record in and tell me if
>>>>it errors" iteration. Just leave that running and get on with something
>>>>else productive.
>>>
>>>I think the point is, if the driver error messages were a little more
>>>intelligent (including some context) to begin with, then you (and a
>>>bazillion others) wouldn't have to take any extra time to begin
>>>with. It would be an instant "Oh, I see the problem."
>>
>>As far as I see, it's MS-Access not the ODBC driver which rsports the
>>*Overflows*.
>
>
> How can you tell?
I can reproduce a similar (not sure if exactly the same) case here.
When I run the 1 row test case with mylog output and ODBC trace on,
I find a SQLTransact(.., SQL_ROLLBACK) call suddenly after some
SQLBindParameter calls in the trace log without any surrounding errors.
regards,
Hiroshi Inoue
From | Date | Subject | |
---|---|---|---|
Next Message | Bart Samwel | 2006-03-17 10:22:58 | Re: Most recent driver aborts transaction after one error |
Previous Message | Randy Yates | 2006-03-16 23:58:43 | Re: psqlODBC Unicode 8.01.02.00 Driver "Overflows" On MS-Access |