Re: Most recent driver aborts transaction after one error

Bart Samwel wrote:

> Hiroshi Inoue wrote:
>
>> Bart Samwel wrote:
>>
> After working around some problems, my test situation worked
> perfectly. Thanks for the hint!
>
> These were the problems I encountered:
>
> 1. SQLGetInfo(SQL_DBMS_NAME) returns "PostgreSQL35W", and
> SQLGetInfo(SQL_DBMS_VER) returns a number in the 07.30 range, while
> I'm running PostgreSQL 8.1. I think that "PostgreSQL35W" is fine for a
> SQL_DRIVER_NAME, but SQL_DBMS_NAME should be simply "PostgreSQL", and
> SQL_DBMS_VER should return the DBMS version, not the driver version
> (which should be returned by SQL_DRIVER_VER).

I will examine it.
Thanks.

>
> 2. I also encountered an access violation while exiting. The call
> stack was not very informative:
>
> ntdll(dot)dll!_RtlpWaitForCriticalSection(at)4() + 0x5b
> ntdll(dot)dll!_RtlEnterCriticalSection(at)4() + 0x46
> psqlodbc35w.dll!023a097e()
> ntdll(dot)dll!_RtlpFreeDebugInfo(at)4() + 0x57
> ntdll(dot)dll!_RtlDeleteCriticalSection(at)4() + 0x78
>
> If you want me to try this with a debug-compiled psqlodbc35w, just say
> the word!

It looks like a thread is about to Free a Handle while another thread is
wating for the Handle.
OK please send me the mylog output.

regards,
Hiroshi Inoue