Hello,
As i alsways wanted to test if I can move teh local MySQL Database to my Syology I played around a little. Synology is providing MariaDB instead of MySQL - if this has any major advantages - don't know - read something about better performance and no oracle overhead. Anyway - as it is teh only one availible it was teh way to go.
After some failures - I found teh settings required to make it happen:
- As MariaDB on Linux Systems is by default case sensitive - I would recommend to turn this off. To do this the local my.cnf needs to be modified and teh synology restarted to activate the setting
/etc/mysql/my.cnf
[mysqld]
lower_case_table_names =1
why? Because if a plugin developer is using for creation of a table mptvdb instead of the name MP uses during creation (MpTvDb) it won't work.
- Second - you need to create a user - using root won't work.
Basicall that's it. I'm also running JMMServer now on MariaDB and until now I didn't see any impact.
As i alsways wanted to test if I can move teh local MySQL Database to my Syology I played around a little. Synology is providing MariaDB instead of MySQL - if this has any major advantages - don't know - read something about better performance and no oracle overhead. Anyway - as it is teh only one availible it was teh way to go.
After some failures - I found teh settings required to make it happen:
- As MariaDB on Linux Systems is by default case sensitive - I would recommend to turn this off. To do this the local my.cnf needs to be modified and teh synology restarted to activate the setting
/etc/mysql/my.cnf
[mysqld]
lower_case_table_names =1
why? Because if a plugin developer is using for creation of a table mptvdb instead of the name MP uses during creation (MpTvDb) it won't work.
- Second - you need to create a user - using root won't work.
Basicall that's it. I'm also running JMMServer now on MariaDB and until now I didn't see any impact.