Re: [INTERFACES] iodbc interface on Unix

Thomas G. Lockhart wrote:

> OK, so there are some minor problems in compiling for the Unix
> environment, most of which I've fixed or worked-around. The biggest
> minor problem, and easiest to fix, is that there is an
>
> #include <config.h>
>
> in most of the files. I believe that this should be changed to
>
> #include "config.h"
>
> to allow the compiler to pick up the file from the local directory.
> Otherwise, it is interpreted as a "system-ish" file and (with my
> Makefile, using many of the compiler options from the Postgres
> distribution) finds the config.h in the Postgres distribution instead.
>

Makes sense to me.

> There is some funny-business with "HINSTANCE", but I've #define'd it to
> be the same as a pointer to void.
>
> As was the case a few weeks ago, I'm now able to start to initiate a
> connection into a database. The only additional problem there is that
> ApplixWare is sending a DSN keyword with a trailing blank, so I'm having
> to chop it off in psqlodbc to find things in the registry.
>
> At this point, I can try connecting to a database, but it doesn't seem
> to get past the first handshaking with Postgres on the wire. I'm
> guessing that the protocol may have changed for v6.4 and those changes
> are not in the driver I'm using? The protocol has settled down for the
> next release, so perhaps we could incorporate the changes into my test
> code.
>

Yes, if you are using a snapshot of 6.4 then the driver won't work because it is using 6.3 protocol. And it uses PG_PROTOCOL_LATEST
in its connect for the protocol version. Maybe it should use 6.3.

How do you set the protocol version to be 6.3? Is it just major number = 6 and minor number = 3? Seems too simple.

Also, as far as compiling goes, I understand the driver has trouble compiling under Linux since the Translation DLL stuff was
added. Did you have to ifdef that stuff out for Non-win32? If so, I guess I'll just put that into the official source.

Byron