mysql / mariadb no longer seems to work. #1074
-
It had been a while since I updated. So attempted to upgrade my manual install from 0.16.8 to 1.0.1. Once I got to the step to run "python manage.py migrate" things failed: Don't believe tsvector type is a data type know to mysql / mariadb. I believe that would fall under LONGTEXT in mysql/mariadb. I'm guessing I'll have to migrate to postgress with pgloader unless someone knows of a solution besides migrating. I don't really know postgresql, but knew at least a bit about mysql/mariadb, which was the reason I ran it on my internal web server. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 11 replies
-
That is possible, i always tought django migrations would be DB agnostic but maybe something in the full text search update broke that. I recommend strongly to use postgresql as the application is not tested against mariadb. |
Beta Was this translation helpful? Give feedback.
That is possible, i always tought django migrations would be DB agnostic but maybe something in the full text search update broke that. I recommend strongly to use postgresql as the application is not tested against mariadb.
If you have any questions during the migration feel free to ask and i will see what i can do.