[unixODBC-support] Named Driver vs full path for Driver

Nick Gorham nick at lurcher.org
Thu Jan 8 16:55:05 GMT 2009


Jeff Martin wrote:

>If the section entry for a DSN in an odbc.ini file uses a full path
>for the Driver entry, will any of the content of odbcinst.ini be used?
>
>
>Suppose the I have the following:
>
>odbc.ini
>======================
>[DsnDriverPath]
>Description=Use a full path for the driver
>Driver=/usr/local/somedb/lib/libodbc.so
>Server=test
>User=test
>{...etc...}
>
>[DsnDriverNamed]
>Description=Use a named driver
>Driver=SomeDB
>Server=test
>User=test
>{...etc...}
>======================
>
>
>
>odbcinst.ini
>======================
>[SomeDB]
>Driver=/usr/local/somedb/lib/libodbc.so
>Threading=0
>=======================
>
>
>
>Will both DsnDriverPath and DsnDriverName "see" the Threading=0 in the
>odbcinst.ini?   Or will only the DsnDriverNamed "see" the Threading=0?
>  
>

No, only DsnDriverNamed as there is no link from DsnDriverName to 
SomeDB. The ability to bipass odbcinst.ini was originally added to cope 
with ini files from older driver managers.

-- 
Nick


More information about the unixODBC-support mailing list