Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
A month ago, I was showing a buddy how use .NET to query MySQL. It worked just fine, but he didn’t understand why we needed a “driver” for MySQL in conjunction with ODBC. He though ODBC would be enough.
When he asked me why, I did my best, but my answer came up short.
What is the correct explanation for this question?
The reason you need a driver is that ODBC is not in itself a driver for talking to databases: it’s an abstraction and an API.
Essentially it is an adaptor layer designed to make all databases appear the same to the client application: you talk to the ODBC library, and it asks the driver manager to fulfill your request using the correct database (based on your connection string).
In order for your database brand to be compatible with ODBC therefore it must provide a driver which implements the required API in order that it can service requests from clients using the ODBC functions.