Re: psqlODBC Unicode 8.01.02.00 Driver "Overflows" On MS-Access

From: Randy Yates <yates(at)ieee(dot)org>
To: pgsql-odbc(at)postgresql(dot)org
Subject: Re: psqlODBC Unicode 8.01.02.00 Driver "Overflows" On MS-Access
Date: 2006-03-16 23:58:43
Message-ID: m3k6audjpg.fsf@ieee.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

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?

>> 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.

I don't understand your statements. Is it not the driver that is performing
the conversions?

If it is MS, then of course that explains everything ...
--
% Randy Yates % "Bird, on the wing,
%% Fuquay-Varina, NC % goes floating by
%%% 919-577-9882 % but there's a teardrop in his eye..."
%%%% <yates(at)ieee(dot)org> % 'One Summer Dream', *Face The Music*, ELO
http://home.earthlink.net/~yatescr

In response to

Responses

Browse pgsql-odbc by date

  From Date Subject
Next Message Hiroshi Inoue 2006-03-17 00:31:05 Re: psqlODBC Unicode 8.01.02.00 Driver "Overflows" On MS-Access
Previous Message Hiroshi Inoue 2006-03-16 23:55:54 Re: Most recent driver aborts transaction after one error