Changes between Initial Version and Version 1 of Ticket #32118


Ignore:
Timestamp:
Oct 18, 2020, 7:59:52 AM (4 years ago)
Author:
Michael
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #32118 – Description

    initial v1  
    1 In the DB world the difference between `float` (4 bytes) and `double` (8 bytes) is arguably common. However Django calls a `double` a `float`. I would imagine it would be very hard to add a `DoubleField` and make `FloatField` the normal 4 byte float due to legacy. Although not ideal how about adding a `SmallFloatField` or `RealField` some other name to allow users to create a 4 byte floats?
     1In the DB world the difference between `float` (4 bytes) and `double` (8 bytes) is arguably common. However Django calls a `double` a `float`. I would imagine it would be very hard to add a `DoubleField` and make `FloatField` the normal 4 byte float due to legacy. Although not ideal how about adding a `SmallFloatField`, or `RealField`, or some other name to allow users to create a 4 byte floats, or raise awareness to when they use a `FloarField`, it may not be what they expect?
    22
    3 PostgresQL calls 4 byte float a `real`, and a 8 byte float a `double precision`
     3PostgresQL calls 4 byte float a `real`, and a 8 byte float a `double precision`:
    44https://www.postgresql.org/docs/9.1/datatype-numeric.html
    55
    6 Mysql calls 4 byte float a `float`, and a 8 byte float a `double`
     6Mysql calls 4 byte float a `float`, and a 8 byte float a `double`:
    77https://dev.mysql.com/doc/refman/8.0/en/floating-point-types.html
    88
Back to Top