Peter Eisentraut wrote:
> Remaining issues:
>
> * libpsqlodbc vs. libodbcpsql: I followed this iODBC/unixODBC schism
> right now, but I'm not sure I like it.
me neither, but once there is a clean set of pg driver code, I can either
remove the unixodbc version of the driver, or use identical code and give the
same name.
> * Shared library version: The driver version shipped with unixODBC has a
> completely different version number than our driver. Does it matter?
> What should we do?
Again, maynot be a issue after the merge.
> * The code still accesses the global odbcinst.ini file directly by name in
> some places, rather than relying on the odbcinst library to find it.
> This should be fixed, but I'm not sure how in each case. Maybe
> something for Nick to look at.
Hmm, what does it need out of odbcinst.ini ? The normal way is a call to
SQLGetPrivateProfileString(.... "odbcinst.ini" );
BTW, its worth making sure the name of the ini file in the call to
SQLGetPrivateProfileString is in lower case. unixODBC doesn't care, but the
Merant DM, which I think is a direct port of the Windows one, doesn't seem to
know that files are case sensitive, so will try and open the file with the
UC name and fail.
Thats the only change I had to make to get our interbase driver working
transparently with either libodbcinst
--
Nick Gorham
Don't worry, be happy
