Just so you know I use and have contributed to unixODBC and I don't use iODBC.
Unicode support
unixODBC follows MS ODBC Driver manager and has SQLWCHARs as 2 bytes UCS2 encoded.
iODBC I believe uses wchar_t (this is based on attempting to support iODBC in DBD::ODBC)
cursor library
unixODBC has one, I don't "think" iODBC has.
application support
A lot of ODBC applications support unixODBC e.g., OpenOffice and ODBC drivers from Oracle, IBM and SAP. I'm not sure about iODBC.
OS support
iODBC has always been the most used on on Macs since Apple included it (although I believe it is removed from Lion). Both can be built from source and most Linux distributions package both (although not Novell/Suse which only distributes unixODBC).
thread safety
unixODBC is thread safe and includes flags to protect handles at different levels. This did not used to be the case with iODBC (but that might have changed now).
support
Both have support forums (unixODBC has 3) although I'd say the unixODBC ones are far more active (I'm on both).
Licensing
unixODBC is GPL and LGPL.
iODBC is LGPL/BSD
In practice there is not a lot of difference but I think you'll find unixODBC is more widely used.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…