Dmitry Russ
Dmitry Russ
@ishikawa thank you. Hm, I need to rethink, what would be better solution. Are you passing binary data with ecto or directly with `mariaex`?
The same size value or different value?
Hi! I'm for second possibility, make it more extensible. Probably, we need to check, how postgres handles it and make something in the way.
I have checked, documentation, there exists `ProtocolBinary::MYSQL_TYPE_GEOMETRY`, till it is not extensible in MySQL / MariaDB, we should support this types natively.
This 2 functions are relevant: https://github.com/xerions/mariaex/blob/master/lib/mariaex/query.ex#L100 and this: https://github.com/xerions/mariaex/blob/master/lib/mariaex/query.ex#L194 for decoding/encoding. Probably we need extensibility for decoding from Point to generic Geometry type and back.
It something not related to secure_auth, as I have the same settings: ``` MariaDB [(none)]> show variables like "%auth%"; +---------------+-------+ | Variable_name | Value | +---------------+-------+ | secure_auth | OFF...
Thanks for clarification, I'll try to install version of MySQL in .travis and test it.
Would be nice, if it possible to provide .travis configuration for testing this case, thats would help a much.
Many thanks for helping reproduce it. I'll definitely test it this weekend.
@shadabahmed - sorry, I was away for a more weeks, I wasn't able to work, but will work this weekend. Sorry for such long time.