Support for MariaDB? about crystal-mysql HOT 3 OPEN

And to be clear that means crystal-mysql would not be able to guarantee the type of a scalar value. Which is not great. But I think this can be handled by crystal-db directly if we allow some type conversions (ie: rs.read returned an Int32, but the user is calling rs.read(Int64), I imagine this to allow runtime type mismatch since that is already the case if db types are different from what user wrote in the code).

from crystal-mysql.

I'm fine accepting maria-db issues. It would like it to be an alternative for users.

Those specs that are failing are because it seems mariadb and mysql do not agree on the type on a select 1.

The following works with maria-db (but will not with mysql)

  sample_value 1, "int", "1" # , type_safe_value: false
  sample_value 1_i64, "bigint", "1", type_safe_value: false
  # ...
  sample_value -1, "int", "-1" # , type_safe_value: false
  sample_value -1_i64, "bigint", "-1", type_safe_value: false

With type_safe_value: true (default) the select_scalar_syntax will be used with the expression directly, in this case select 1 and select -1. And the specs will validate the result set should read the first column of the first row will have the same value and type as the first argument. So mysql returns something that translates to Int64 while maria-db something that translates to Int32.

I could not find any documentation regarding this differences.

So the actionable thing is probably to:

1. Add mariadb to the CI
2. Make specs pass on both

from crystal-mysql.

Hello @bcardiff, thanks for your response and your patience, missed this in my inbox.

Thanks for providing the details, I was able to find the reference about that change in MDEV-16347, indicating that the change was intentional from MDEV-12619.

Perhaps the spec/test can be adjusted to evaluate first the data type of CREATE TABLE t1 AS SELECT 1 AS c1 and from there determine the type?

Cheers.

from crystal-mysql.