"Dave Page" <dpage@vale-housing.co.uk> writes:
> I thought unixODBC was merely the driver manager - didn't realise they
> had some drivers as well, hence why I assumed the problem was with
> psqlODBC.
No, they've got a pile of embedded drivers:
$ du unixODBC-2.2.8/Drivers
132 unixODBC-2.2.8/Drivers/MySQL/samples
1928 unixODBC-2.2.8/Drivers/MySQL
994 unixODBC-2.2.8/Drivers/PostgreSQL
1054 unixODBC-2.2.8/Drivers/Postgre7.1
88 unixODBC-2.2.8/Drivers/txt/doc
736 unixODBC-2.2.8/Drivers/txt
22 unixODBC-2.2.8/Drivers/odbc
436 unixODBC-2.2.8/Drivers/template
516 unixODBC-2.2.8/Drivers/MiniSQL
570 unixODBC-2.2.8/Drivers/nn
6292 unixODBC-2.2.8/Drivers
I have not tried to compare carefully, but judging by the snippet you
just posted versus the KSQO-related code I just grepped for, what's in
unixODBC is a rather distant ancestor of the present psqlODBC. I am not
too sure what the MySQL driver is doing in there either ... I know there
is a separately maintained MyODBC package ...
regards, tom lane