Update to 0.55.3 breaks MySQL 5.7 models

Bug reports
1

I'm currently using Metabase 0.54.8 and it is connected to a MySQL 5.7 database working flawlessly.

Now, i tried to update to the 0.55.3 version and the upgrade went fine. I'm running metabase from a Docker Container. I just pulled the new version as always.

Now, when i get into some models that have a user defined column, that only divides one value on another, now have a mysql syntax error.

Seems now to be converting the values to double using cast, but 5.7 does not have double.

So my question is. Is this the end for metabase support for mysql 5.7?

image

image
image894×675 43.9 KB

image
image740×347 15.5 KB

3

Here's how the model looks before upgrading to 0.55.3

image
image855×341 25.4 KB

The results shown properly before upgrading to 0.55.3

image
image266×262 3.02 KB

The column definition:

image
image414×175 4.19 KB

4

Also tried updating to 0.55.4 and the same thing happens. All queries generated in metabase on a MySQL 5.7 Database, have a syntax error when the query has a decimal value in them.

The SQL Query generated by the "query generator" casts the values as DOUBLE when that type does not exist in MySQL 5.7

Is this going to be addressed?

Thanks a lot in advance

5

Honestly, I don't think we'll address something which is no even longer maintained by the database engine creator. MySQL 5.x is already EoL, we can't start doing checks all across our code due to old versions of applications

6

Fair enough.
Thanks a lot for your answer