DB Server Versions Documentation

[Benton, Kevin]

Does anyone besides me think we should consider putting together a matrix of database versions we support with MySQL versus our Bugzilla versions so we can point Bugzilla Administrators to it?  I'm thinking that table might look *something* like this (from ... to ...):

...

       Supported Bugzilla Database Engine Versions
+----------------------------+--------+--------+--------+
|           Bugzilla Version | 2.18.x | 2.20.x | 2.22.x |
+----------------------------+--------+--------+--------+
| MySQL 3.23.x               |  Yes   |  No*   |  No*   |
+----------------------------+--------+--------+--------+
| MySQL 4.0.13 and earlier   |  Yes   |  No*   |  No*   |
+----------------------------+--------+--------+--------+
| MySQL 4.0.x (14+)          |  Yes   |  Yes   |  Yes   |
+----------------------------+--------+--------+--------+
| MySQL 4.1.x                |  Yes   |  Yes   |  Yes   |
+----------------------------+--------+--------+--------+
| MySQL 5.0.x                |  No    |  Yes   |  Yes   |
+----------------------------+--------+--------+--------+
| PostgreSQL 8.0.x           |  No    |  Yes   |  Yes   |
+----------------------------+--------+--------+--------+
 * = Bugzilla support for this DB version has ended.

Database engines not listed in the table above have either not been tested or do not work with Bugzilla.

The recommended production database engine for Bugzilla 2.22.x is the latest stable release of:

MySQL 4.1.x

...

I suggest we limit to this kind of reporting (major & minor versions known to work) rather than some form of "x.y.z and greater".  I make the suggestion because we haven't seen the feature set for version x+1 or y+1 yet and therefore, we have no way to know if a database code change will impact Bugzilla.

---
Kevin Benton
Perl/Bugzilla Developer/Administrator, Perforce SCM Administrator
AMD - ECSD Software Validation and Tools
 
The opinions stated in this communication do not necessarily reflect the view of Advanced Micro Devices and have not been reviewed by management.  This communication may contain sensitive and/or confidential and/or proprietary information.  Distribution of such information is strictly prohibited without prior consent of Advanced Micro Devices.  This communication is for the intended recipient(s) only.  If you have received this communication in error, please notify the sender, then destroy any remaining copies of this communication.