still looks like DOUBLE should be dealing with Python floats.
DOUBLE_PRECISION in the Oracle dialect is also Float and doesn't
default to decimal coercion.
We can fix this problem, it's just one of those changes that you have
to warn users like crazy on and then just do the change on a major
FWIW, that PR would have been during MySQL5.0 - not 5.5.
5.0 was released in October 2005; 5.1 was not released until November 2008
assuming the 5.0 docs...
>
> https://docs.oracle.com/cd/E19078-01/mysql/mysql-refman-5.0/data-types.html#numeric-types
looking deeper at their docs, this bit
Interesting. Thank you for the extensive explanation.
pon., 29 kwi 2019 o 19:49 Mike Bayer napisał(a):
> On Mon, Apr 29, 2019 at 1:13 PM mdob wrote:
> >
> > Just out of curiosity, why it was decided that MySQL DOUBLE, which is
> approximation, will be presented in ORM as Decimal by default
On Mon, Apr 29, 2019 at 1:13 PM mdob wrote:
>
> Just out of curiosity, why it was decided that MySQL DOUBLE, which is
> approximation, will be presented in ORM as Decimal by default instead of
> float?
>
> MySQL DOUBLE -
> https://dev.mysql.com/doc/refman/5.5/en/floating-point-types.html
>
Just out of curiosity, why it was decided that MySQL DOUBLE, which is
approximation, will be presented in ORM as Decimal by default instead of
float?
MySQL DOUBLE -
https://dev.mysql.com/doc/refman/5.5/en/floating-point-types.html
SQLAlchemy DOUBLE -
