[SectionName1] key1 = value1 key2 = value2 ... [SectionName2] key1 = value1 key2 = value2 ...
Each ODBC driver has its own section and can be referred to by the name of its section. Configuration keys recognised in driver sections by unixODBC itself are:
The section named [ODBC]
Enable ODBC driver trace output, which is written to the path specified by TraceFile
Note that some drivers have their own separate trace control options. Unlike the Trace option these are usually specified at the DSN level.
Values recognised as enabled are any case variation of "1", "y", "yes" or "on".
Path or path-pattern to write the ODBC trace file to. Has no effect unless Trace
WARNING: setting TraceFile to a path writeable by multiple users may not work correctly as only the first user will be able to create and open the file.
[PostgreSQL] Description = PostgreSQL driver for GNU/Linux Driver = /usr/lib/psqlodbcw.so Setup = /usr/lib/libodbcpsqlS.so FileUsage = 1
Note that driver paths may vary, and some drivers require Driver64 and Setup64 entries too.
By specifying the driver like that, you can then reference it in the odbc.ini(5) as follows:
Driver = PostgreSQL
The recommended way to add that driver is by creating a template file containing:
[PostgreSQL] Description = PostgreSQL driver for GNU/Linux Driver = /usr/lib/psqlodbcw.so Setup = /usr/lib/libodbcpsqlS.so
and call the odbcinst(1):