P4DTI issue job002084

TitleP4DTI does no MySQL version detection
Assigned userNick Barnes
DescriptionSome aspects of P4DTI Bugzilla operation depend on particular versions of MySQL. For instance, Unicode character set support was introduced with MySQL 4.1. Some more recent versions of MySQL are experimental or beta releases and are not supported. The P4DTI does not detect the current version of MySQL, so cannot warn if the version is unsupported or deprecated.
AnalysisThis arose when improving the Unicode replication support; MySQL 4.0 does not have the necessary character set support to allow us to determine or specify per-table and per-column encodings.
The MySQL command "show variables like version" is our friend. The string reported is not simply a.b.c, but can be, for instance, "5.1.27-community-nt". We need a table of supported versions (note that version 5.1 has recently come out of beta and should now be supported), and different messages/actions depending on the detected version.
How foundinspection
EvidenceI just know.
Observed in2.4.3
Created byNick Barnes
Created on2009-04-14 12:55:53
Last modified byNick Barnes
Last modified on2009-04-14 13:27:05
History2009-04-14 NB Created.


Change Effect Date User Description
167771 closed 2009-04-14 12:48:37 Nick Barnes Improve MySQL version detection, Unicode configuration detection, Unicode replication testing, and error handling in the presence of Unicode strings.