The file can be updated by using the odbcinst utility (recommended) or edited by hand.
[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 that section in files such as odbc.ini. Within each section, unixODBC also recognises the following configuration keys:
Some ODBC drivers have their own trace control options. Unlike the Trace option, these separate options are usually specified at the Data Source Name (DSN) level.
Trace will be enabled if the corresponding value contains any case variant of "1", "y", "yes" or "on".
WARNING: Setting TraceFile to a path writable by multiple users might not work correctly, as only the first user will be able to create and open the file.
Template files use the same format as odbcinst.ini.
[PostgreSQL] Description = PostgreSQL driver for GNU/Linux Driver = /usr/lib/psqlodbcw.so Setup = /usr/lib/libodbcpsqlS.so FileUsage = 1
Driver paths can vary, depending on your operating system and whether your distribution is multi-arch enabled. Some drivers also require Driver64 and Setup64 entries.
The above section can be referenced in odbc.ini as follows:
Driver = PostgreSQL
The recommended way of adding the PostgreSQL driver to your system 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 calling odbcinst as follows:
"The unixODBC Administrator Manual (HTML)"
For a full list of contributors, refer to the AUTHORS file.