Mariaex incorrectly selects boolean type for TINYINT(4) about mariaex

[liveforeverx]

Yes, it is because MySQL doesn't have boolean type. And, INT tiny represents it, but there is no way to get from MySQL tyne(1) or tiny(10) it is (checking).

[liveforeverx]

If you will try to save to tiny INT the value 0 or 1, than it is impossible by reading to get right representation, if it is boolean(true, false) or int(0, 1). Is it possible to avoid tiny INTs for integers in your setup?

[nathanjohnson320]

No I'm running a model generation script on a legacy database where the TINY ints are already setup. Is there no way to check the NUMERIC_PRECISION column in information schema to grab the size and set it as an integer/boolean based on that?

[nathanjohnson320]

Actually I guess you can't because it's always 3 for tinyints.

[liveforeverx]

To: @laurocaetano @josevalim
May be it make sense to decode tiny int always as int and cast 0, 1 to boolean on ecto side, where model types are available?

@nathanjohnson320 at least, on binary protocol it doesn't send any information about precision.

[josevalim]

@liveforeverx yes, we could do that. Once you change the behaviour in mariaex and release new version, please open up an issue in Ecto so we can fix it. Also, please release it as 0.3. :)

[liveforeverx]

@josevalim , off course, it is backwards incompatible change.