As you suggested, I created separate mix project with ecto and minimal migrations and model to replicate this issue: GitHub - revati/ecto_mysql_bug · GitHub
revati
eljorge
eljorge
revati
this isn’t exactly the same as this example. As shown in binary id odd bug · Issue #2602 · elixir-ecto/ecto · GitHub
# insert query
INSERT INTO `my_modules` (`id`) VALUES (?) [<<246, 200, 234, 122, 29, 144, 70, 72, 176, 30, 56, 120, 54, 0, 135, 84>>]
# select query
SELECT m0.`id` FROM `my_modules` AS m0 WHERE (m0.`id` = ?) [<<246, 200, 234, 122, 29, 144, 70, 72, 176, 30, 56, 120, 54, 0, 135, 84>>]
ecto doesn’t use MySQL functions to convert to binary and vice versa.
0
eljorge
We changed the collation set of our DB from latin1_swedish (defaulton mysql 5.7) to ut8 and it solved our problem
2