#5282 Document MySQL migration issue
Merged 2 years ago by ngompa. Opened 2 years ago by zlopez.
zlopez/pagure docs  into  master

file modified
+8
@@ -42,6 +42,14 @@ 

  

  * LOGGING_GIT_HOOKS

  

+ .. warning:: When upgrading MySQL database you can encounter issue with

+        incompatible columns. In this case try to check the collation of the

+        mentioned column by ``show full columns from <table>;`` in ``mysql``.

+        If the collation is something else then `utf8` you need to convert

+        your database to `utf8` first. See

+        `this guide <https://stackoverflow.com/questions/1294117/how-to-change-collation-of-database-table-column>`_

+        for how to do it or if you have SQL script for db setup,

+        you can change it directly in the script.

  

  From 5.9 to 5.10

  ----------------

Document solution for the https://pagure.io/pagure/issue/5219 in pagure
documentation.

Signed-off-by: Michal Konečný mkonecny@redhat.com

Should we include this in the UPGRADING doc?

It probably makes sense to put it in UPGRADING.

I must have missed the UPGRADING doc. Should I move it to UPGRADING or keep it on both places?

I think it should be moved to UPGRADING. It doesn't affect fresh installs, right?

@ngompa You are right, it doens't.

I will move it to UPGRADING.rst, I just need to find the correct version that the migration script is related to.

rebased onto 3a32d9e

2 years ago

I moved the warning to UPGRADING.rst

Pull-Request has been merged by ngompa

2 years ago
Metadata