| 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-16 23:43:26 |
| Message-ID: | 4419F81E.6070708@tpf.co.jp |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
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*.
> It might also be helpful if the driver converted all records it was
> able to convert and not simply abort on the first record with an
> error.
Unfortunately the ODBC driver itself doesn't detect any error before
MS-Access calls SQLEndTran.
regards,
Hiroshi Inoue
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hiroshi Inoue | 2006-03-16 23:55:54 | Re: Most recent driver aborts transaction after one error |
| Previous Message | Hiroshi Inoue | 2006-03-16 23:36:17 | Re: updatable cursors |