Details
-
Bug
-
Resolution: Handled by Support
-
Low
-
None
-
3.0.3
-
None
-
MySQL 4.1.9
-
3
-
Description
I suspect there is a bug in the code that upgrades the DB from older releases of Jira to 3.03. To my recollection, I have updated twice up to 3.03 but I don't recall the exact details.
I have recently upgraded to MySQL 4.1.9 and I noticed this in my Tomcat logs the next time I restarted:
[core.entity.jdbc.DatabaseUtil] WARNING: Column "AUTHOR" of table "jiraaction" of entity "Action" has a column size of "85" in the database, but is defined to have a column size of "255" in the entity definition.
[...]
I get this warning for exactly 157 different columns in different tables. I tried updating them by hand but it's taking way too long.
When Jira finds such a mismatch, there should be a way for us to tell it to automatically update the DB to reflect the entity definition. Especially if the DB size is smaller than the entity definition, it should automatically update the DB since there is no risk of data loss.
I filed this as a bug instead of a RFE because the DB should have never gotten into this bad state in the first place...