psqlODBC Experimental Enhanced branch

Some time ago I posted a message to the list pre-announcing the release
of an experimental version of psqlODBC. This release is now available
for testing and evaluation purposes from:

http://pgfoundry.org/frs/?group_id=1000125

THIS FILES ARE RELEASED FOR TESTING AND EVALUATION ONLY AND Are NOT
RECOMMENDED FOR PRODUCTION USE!

This release is based on a code branch made at roughly v07.03.0260 of
psqlODBC, and has been enhanced by Hiroshi Inoue and Hiroshi Saito to
include a similar feature set to the 08.01 driver series, specifically
with the addition of Kerberos and SSL support through the use of libpq,
as well as other changes detailed in the release notes.

This branch differs from 08.01 in that the libpq integration has been
approached in a totally different way to that taken by Anoop and Siva at
Pervasive. Of particular note is the this drivers ability to

The purpose of this release is to evaluate which libpq driver, 08.01 or
07.03 will make the most suitable basis for future psqlODBC versions.
Please test and evaluate it, examine the source code, benchmark it and
anything else you can think of, and post any opinions to the mailing
list. Bear in mind that this experimental branch has not had anything
like the testing that 08.01 has, and that any resulting bugs need not
necessarily mean that it is not the better driver to continue
development with.

Regards, Dave.

From: "Dave Page"

>Please test and evaluate it, examine the source code, benchmark it and
>anything else you can think of, and post any opinions to the mailing
>list.

Hi Dave;

I have experienced an inconsistent error with all versions of the 8.1
driver up to an including 8.1.1.1. I don't get any error via ODBC but the
Microsoft "Unfortunately Microsoft has encountered an error and must exit
the application..." dialog box.

I have never experienced this problem with the 7.02 branch up to 7.02.00.05.

I installed 7.02.026 on February 22 and did not encounter any problem until
this morning.

I am running PostgreSQL 8.1.0 on i686-pc-mingw32, compiled by GCC gcc.exe
(GCC) 3.4.2 (mingw-special).

I am running a VB.NET 2003 application accessing the database (obviously)
via ODBC.

I cannot find any error notification in mylog or the psqlodbc log. In the
Windows event viewer the error message is:

Event Type: Error
Event Source: COM+
Event Category: Unknown
Event ID: 4786
Date: 28/02/2006
Time: 10:18:37 AM
User: N/A
Computer: DELL4500
Description:
The system has called a custom component and that component has failed
and generated an exception. This indicates a problem with the custom
component. Notify the developer of this component that a failure has
occurred and provide them with the information below.
Component Prog ID: 0[ODBC][C:\Program
Files\psqlODBC+\bin\psqlodbc35w.dll]
Method Name: IDispenserDriver::CreateResource
Process Name: FormsTest.exe
Exception: C0000005
Address: 0x036F5AFF
Call Stack:
psqlodbc35w!SQLGetDiagFieldW + 0x2AF

The error is totally inconsistent - I can go for days without experiencing
any problem; at other times it occurs frequently.

Any thoughts?

Regards,
George

George Weaver wrote:
>
> From: "Dave Page"
>
>> Please test and evaluate it, examine the source code, benchmark it and
>> anything else you can think of, and post any opinions to the mailing
>> list.
>
>
> Hi Dave;
>
> I have experienced an inconsistent error with all versions of the 8.1
> driver up to an including 8.1.1.1. I don't get any error via ODBC but
> the Microsoft "Unfortunately Microsoft has encountered an error and must
> exit the application..." dialog box.
>
> I have never experienced this problem with the 7.02 branch up to
> 7.02.00.05.
>
> I installed 7.02.026 on February 22 and did not encounter any problem
> until this morning.
>
> I am running PostgreSQL 8.1.0 on i686-pc-mingw32, compiled by GCC
> gcc.exe (GCC) 3.4.2 (mingw-special).
>
> I am running a VB.NET 2003 application accessing the database
> (obviously) via ODBC.
>
> I cannot find any error notification in mylog or the psqlodbc log.

Is there nothing in mylog output ? If so, are you turning on the Mylog
option in the "Pre-connection/default logging options" box ?
If thers's something in mylog, please send it to me.

regards,
Hiroshi Inoue

----- Original Message -----
From: "Hiroshi Inoue"

> Is there nothing in mylog output ? If so, are you turning on the Mylog
> option in the "Pre-connection/default logging options" box ?
> If thers's something in mylog, please send it to me.

Hi Hiroshi,

Attached is a copy of the last mylog file when the error occurred.

Regards,
George

----- Original Message -----
From: "Hiroshi Inoue"

>
> Are you turning on the mylog option per DataSource ?
>

No, the log I forwarded was from the Global mylog setting. I have now set
to DataSource, but I'll have to wait until the error recurs before I can
forward a copy of the log....

Am I correct that only one of the sources should be set? I have unchecked
the mylog setting for Global.

Regards,
George

George Weaver wrote:

>
> ----- Original Message ----- From: "Hiroshi Inoue"
>
>>
>> Are you turning on the mylog option per DataSource ?
>>
>
> No, the log I forwarded was from the Global mylog setting. I have now
> set to DataSource, but I'll have to wait until the error recurs before
> I can forward a copy of the log....
>
> Am I correct that only one of the sources should be set? I have
> unchecked the mylog setting for Global.

Please check both for debugging.

regards,
Hiroshi Inoue