| Title | P4DTI does no MySQL version detection |
| Status | closed |
| Priority | essential |
| Assigned user | Nick Barnes |
| Organization | Ravenbrook |
| Description | Some 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. |
| Analysis | This 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 found | inspection |
| Evidence | I just know. |
| Observed in | 2.4.3 |
| Created by | Nick Barnes |
| Created on | 2009-04-14 12:55:53 |
| Last modified by | Nick Barnes |
| Last modified on | 2009-04-14 13:27:05 |
| History | 2009-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. |