The short answer is that there are three people in two companies based in the same small area of the same European country who are constantly going into the Wikipedia article for ODBC and "rewriting history", slamming each other's products, making false statements, etc. You can see this by entering the Wikipedia article on ODBC and clicking on the "View History" tab. It has caught the attention of the Wikipedia administrators, resulting in the warnings displayed in the article. Since the definition of ODBC technology in Wikipedia is the subject of a "wiki war" between those two companies, we have never participated in the Wikipedia and have looked on in horror as other ODBC tech vendors in Canada and the US have tried to participate and essentially been "run over". It should also be noted that those two companies that are engaged in "wiki combat" also engage in a lot of other strange behavior, such as one having registered the most obvious DNS name for the website of the other (even going so far as to setup a fake corporate entity to rebuff legal challenges).
It's also worth noting that the modus operandi
of these two companies locked in mortal conflict has been to create so-called ODBC "Driver Manager" components for some non-
Windows platforms which they then give away for free ("the first one's always free" isn't it?). The first red flag is obviously that you have multiple companies giving away ODBC "Driver Manager" components for the same exact non-
Windows platforms, and none of them are involved with the development of those platforms. The second red flag is that no major database vendors support either of these ODBC "Driver Managers" in a consistent way. These two companies then go to platform vendors like Apple and Canonical and pitch the idea that their "free" ODBC "Driver Manager" should be included with that platform as a "standard". The resulting "standards fraud" draws vendors, developers and users into a spiderweb where they're exposed to what they think is "open source", but which is actually a runtime system for those companies' totally proprietary non-
Windows ODBC drivers. Apple, in fact, recently ripped all of that stuff out of their platform (in SnowLeopard 10.6) and we hope Canonical and others do the same, because the bottom line is that there are no well-supported ODBC drivers for non-Windows platforms
and the only viable solution is to use server-based ODBC with the database vendors' officially supported Windows ODBC drivers. Server-side ODBC is why we created ODBC ROUTER --initially in support of Macs, today for iPad, iPhone/iPod Touch, Linux and even Windows.