|
MySQL 5.0 has been out for a while now, and our company has standardized on it as the version for our MySQL servers. I hope this platform is officially supported by Atlassian soon.
I hope Mysql 5 will be supported as soon as possible!
I've just been told that MySQL 5.0 and several other core applications are going to be replacing their aging counterparts on our production servers. There is a request that we keep our JIRA/Confluence server at the same revision as the rest of the systems. I'd like to be able to tell them to go ahead.
Is there an ETA, or a list of items that need to be addressed, and/or something we can do to assist in this process? We will be unable to upgrade our OS because MySQL 5.0 will be the only supported version. I hope that you will work on supporting MySQL 5.0 for Confluence soon!
This issue is currently scheduled to be addressed for Confluence 2.6 (mid-June), although we obviously can't make a firm commitment. We haven't yet done any testing against this configuration, and thus don't know what issues, if any, we will encounter.
That said, I believe a number of people are already using Confluence 2.4 successfully with MySQL 5, despite the lack of official support. So we're cautiously optimistic. I hope that you will work on supporting MySQL 5.0 for Confluence soon!!!!!!
Just for the record, we had a local issue (more info in CSP-9986) with MySQL 5.0.5 and Confluence 2.5.4 (both running on OS X 10.4) where after creating a user with username "fightclub", you could not create a group with name "fightclub", however you could create a user with the same username as an existing group. Looking at the database, it appears that users and groups are stored in the "os_user" and "os_group" tables but there are no rows in either the "users" or "groups" tables. Also there were no rows in the "os_group" table containing "fightclub", so it would appear that the application is mistakenly reporting "A group with this name already exists" even though it doesn't. In addition, with default log4j.properties settings, there is no logging of this event when this issue occurs. Because of this, I'm switching to a different database that is supported for future confluence plugin development for Confluence 2.5.x (one that is listed here http://confluence.atlassian.com/display/DOC/Confluence+Installation+Guide
 ). Nevermind... seems that both MySQL 5.0.5 and MySQL 4.1.22 have the aforementioned issue (CSP-9986).
For those interested, I have been advised by support that this is due to be fixed in Confluence 2.6, which is due in roughly 6 weeks from today
Hi everyone,
We now have established a regular build and test configuration using MySQL 5.0 and as such it is now a supported database when used with Confluence 2.5 and above. Cheers, |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
New Feature
Resolved
Major
Officially support mySQL 5.0
Users wishing to install 5.0 on their own can attempt the instructions at http://confluence.atlassian.com/display/DOC/Database+Setup+For+mySQL