Skip to content

"MySQL-Dialect #1941

@DevPandi

Description

@DevPandi

Description

Hello dear Tempest team,

I think the database system is very good. However, I have noticed one thing that can lead to problems, especially in connection with MySQL/MariaDB.

SQLite and PostgreSQL are not affected by this. The data type ‘TEXT’ is so large in SQLite and PostgreSQL that it is unlimited. In MySQL, however, there are several types of TEXT, and the version selected by the dialect is limited to 65,535 characters. At first glance, this number may seem large, but in a CMS it can quickly become too small if markup language is used.

It would therefore be worth considering whether to change the dialect to MEDIUMTEXT or LONGTEXT. This would make it comparable with PostgreSQL and SQLite.

DevPandi

Benefits

The advantage for developers would be that the database behaviour would be aligned at this point and SQLite, PostgreSQL and MySQL/MariaDB would really ‘behave the same’ - to a large extent at least.

SQLite supports approx. 1 GB, PostgreSQL has no limit for text. MySQL is the exception here. This could result in different behaviour for products that are also offered for others.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions