|
CoreReader
The Universal Access Data Utility |
|
|
home page description documentation countries source specifics policy letter |
|
license free software change log testing requirements database manager date protocol |
|
Disclaimer Brand names are addressed only as a service to CoreReader users. See the source specifics page for details. To add to these notes or to add your favorite data source, see instructions on the source specifics page.
Source The CoreReader development environment includes a MySql server version 3.23.49 running on a Ms. NT4 SP6 Server and a server version 4.018 on win2k. The ODBC drivers used for testing were {MyOdbc} version 2.50.19.00 dated 5 Oct 98 and {MySQL ODBC 3.51 Driver}.
Running With MySql First of all, and this is important, the earlier version of the data socket just plain did not work. This is the Microsoft method of marketing which withholds the limitations to lead one to invest in a product before knowing the facts. It wasted a lot of my time. Let us hope that this is not indicative of the future. ( See the policy letter published on this site. ) The MySql server has SQL limitations which are taking a very long time to correct. For example, it still cannot do a full join. Refer to the MySql documentation about its SQL limitations before running against it. Many of the standard CoreReader queries will fail with misleading error messages. When using a DSN to connect, the MySql data socket seemed to require that a client cursor be specified. The MySql examples in the connection screen have been tested, and all CoreReader MySql connections are copied from them. Part of the power of MySql arises from its ability to run on so many operating systems, but this can create confusion about requirements for object names. Do not let this concern you. CoreReader will handle all naming constraints and conventions on all platforms. To insure compliance with the various naming requirements, regardless of the platform on which MySql is running, simply allow CoreReader to generate and control the names of all objects in the queries. MySql is developing quickly, so feedback on problems encountered and problems cleaned up would be appreciated. This is a volatile industry where companies and products rise and die overnight, so these assessments can change quickly, but at the moment, MySql shows promise.
|
|
This web site is maintained with Notepad. |
|
|
Copyright 2001 - 2010 John Ragan. |
|