Details
-
Suggestion
-
Resolution: Won't Do
-
None
-
None
-
1
-
2
-
Description
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Hi Atlassian
As already commented on JRA-59427 it would be great to see the tables with wrong collation already in the Health checker user interface.
In our case we were also alerted by the health checker and after running the query documented in Confluence we found one table that someone had created for test purposes and indeed this table had the wrong collation
But since it was not relevant for JIRA it could be deleted without impact and the health checker went happy as well.
Our JIRA administrators - which are not database administrators - would have a better feeling if they could judge first if there is a real problem with the database and only bother the database administrators if it is really necessary.
it should not be such a big effort to implement this since the queries are already run by health checker. It's just to give us a little bit more of the already existing information in the UI.
Another option would be to let health checker only check the tables relevant for JIRA but this could become a more difficult task since this might be hard to answer for some tables.
Regards,
Dieter
Attachments
Issue Links
- derived from
-
JRASERVER-59427 Incorrect warning about the use of utf8_general_ci collation on Mysql (Linux).
- Closed
- relates to
-
JRACLOUD-59501 Display tables with incorrect collation in Health Checker user interface
- Closed