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 may have influenced someone: ---- 10.7. Choosing the Right Type for a Column For optimum storage, you should try to use the most precise type in all cases. For example, if an integer column is used for values in the range from 1 to 99999, MEDIUMINT UNSIGNED is the best type. Of the types that represent all the required values, this type uses the least amount of storage. Tables created in MySQL 5.0.3 and above use a new storage format for DECIMAL <https://docs.oracle.com/cd/E19078-01/mysql/mysql-refman-5.0/data-types.html#numeric-types> columns. All basic calculations (+, -, *, and /) with DECIMAL <https://docs.oracle.com/cd/E19078-01/mysql/mysql-refman-5.0/data-types.html#numeric-types> columns are done with precision of 65 decimal (base 10) digits. See Section 10.1.1, “Overview of Numeric Types” <https://docs.oracle.com/cd/E19078-01/mysql/mysql-refman-5.0/data-types.html#numeric-type-overview> . Prior to MySQL 5.0.3, calculations on DECIMAL <https://docs.oracle.com/cd/E19078-01/mysql/mysql-refman-5.0/data-types.html#numeric-types> values are performed using double-precision operations. If accuracy is not too important or if speed is the highest priority, the DOUBLE <https://docs.oracle.com/cd/E19078-01/mysql/mysql-refman-5.0/data-types.html#numeric-types> type may be good enough. For high precision, you can always convert to a fixed-point type stored in a BIGINT <https://docs.oracle.com/cd/E19078-01/mysql/mysql-refman-5.0/data-types.html#numeric-types>. This enables you to do all calculations with 64-bit integers and then convert results back to floating-point values as necessary. all that being said, updating mysql was a chore and often scary then, so most linux distributions and dbas held things back and did not upgrade as aggressively as people have the past 5 years. 3.23/4.1 was likely a core target for SqlAlachemy - not 5.x http://ftp.nchu.edu.tw/MySQL/doc/refman/4.1/en/choosing-types.html http://ftp.nchu.edu.tw/MySQL/doc/refman/4.1/en/numeric-types.html -- SQLAlchemy - The Python SQL Toolkit and Object Relational Mapper http://www.sqlalchemy.org/ To post example code, please provide an MCVE: Minimal, Complete, and Verifiable Example. See http://stackoverflow.com/help/mcve for a full description. --- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
