The Connectors team at MySQL has been reorganized and includes additional resources. It seemed fitting to have a meeting for those working on C/ODBC v5.
We had a week long meeting in Germany at a place called Bad Herrenalb (since 4 of the new resources are living in Germany).
By the end of the meeting we had a revised development plan in place with tasks assigned and target dates set.
MySQL Connector/ODBC is our next generation ODBC driver which allows access to the MySQL server using the ODBC standard - a cross-platform, cross-database C Call Level Interface.
This version is being released to get community feedback but is NOT suitable for production environments. It is now available in binary form from the Connector/ODBC download pages at http://dev.mysql.com/downloads/connector/odbc/5.0.html and mirror sites (note that not all mirror sites may be up to date at this point of time - if you can’t find this version on some mirror, please try again later or choose another download site.)
Install Notes
Please uninstall any existing Connector/ODBC v5 before installing this version.
Changes
MySQL Connector/ODBC is our next generation ODBC driver which allows access to the MySQL server using the ODBC standard - a cross-platform, cross-database C Call Level Interface. This version is being released to get community feedback but is NOT suitable for production environments. It is now available in binary form from the Connector/ODBC download pages at http://dev.mysql.com/downloads/connector/odbc/5.0.html and mirror sites (note that not all mirror sites may be up to date at this point of time - if you can’t find this version on some mirror, please try again later or choose another download site.)
Install Notes
Please uninstall any existing Connector/ODBC v5 before installing this version.
Changes
Whats is it?
ODBC Trace output (also referred to as ODBC logging) is useful when problem solving ODBC issues as it shows the calls made through the various layers of software. ODBC Trace output is often requested by support folks when asked to solve an ODBC issue so including one with a request for help is often going to lead to a faster response.
There are a number of ways, and places, to produce trace output. The two most common trace sources are;
DM Trace Output
Trace output from the DM is usually enough to solve an ODBC issue
and as such is the most interesting for an initial request for
help. This trace is typically turned on/off via an ODBC GUI
Administrator. On MS Windows XP you can find this program in the
“Control Panel -> Administrator Tools” (you may have to turn
on “Classic View” to find …
MySQL Connector/ODBC 5.00.07 Beta 3 has been released. MySQL Connector/ODBC is our next generation ODBC driver which allows access to the MySQL server using the ODBC standard - a cross-platform, cross-database, C, Call Level Interface.
This version is being released to get community feedback but is NOT suitable for production environments. It is now available in binary form from the Connector/ODBC download pages and mirror sites (note that not all mirror sites may be up to date at this point of time - if you can’t find this version on some mirror, please try again later or choose another download site.)
Install Notes
Please uninstall any existing Connector/ODBC v5 before installing this version.
Changes
C/ODBC v5 comes with some command-line tools such as MYODBCShell. MYODBCShell can be used to interact with the server. It is similar to the mysql command-line tool but it uses ODBC. MYODBCShell is very useful for problem solving ODBC issues (more on this in a later blog) and for simply trying out commands before using them in an ODBC application.
Here are some of the unique features of MYODBCShell;
You can use MYODBCShell by entering a command-line shell and
executing the command MYODBCShell. You may have to change to the
directory where MYODBCShell was installed or get it into your
PATH. Execute MYODBCShell without arguments to
get information …
C/ODBC comes with some command-line tools such as
MYODBCInstaller.exe. MYODBCInstaller can be used to;
register/deregister a driver or create/edit/remove a DSN. In
other words - MYODBCInstaller can be used to manage ODBC system
information.
Driver
An ODBC driver must be registered before being used. On most platforms this means adding entries into some text (odbcinst.ini) file. In the case of MS Windows it also means adding entries into the registery. A driver is deregistered by simply removing the entries. One complicating factor is that a UsageCount is maintained. The UsageCount is incremented each time a driver is registered and decremented each time the driver is deregistered. The idea is that the driver files should only be removed if the UsageCount becomes 0.
MYODBCInstaller handles adding/removing entries and inc/dec UsageCount but does NOT copy/remove files - that must be done by the caller. For …
[Read more]The time between Beta 1 and Beta 2 has been dominated by two events;
The end result is a Beta with some improvements;
There is still much to do so look for us to continue with frequent releases.
All of the existing PostBuild tests now succeed. So whats next? Developer testing will continue with;
At the same time QA folks within the orgnization will start to do their thing.
At this point most of the code is in place for Connector/ODBC v5 Beta 1 so the emphasis is on getting all of the Post-Build Tests to pass.