On Monday, February 27, 2017 at 6:50:27 AM UTC+1, Daniel da Silva wrote:
>
> I'm not sure of the design rationale behind including options to specify
> variants of integers, but not floats. We already have SmallIntegerField,
> IntegerField, and BigIntegerField. Why is this not in the same line of
I'm not sure of the design rationale behind including options to specify
variants of integers, but not floats. We already have SmallIntegerField,
IntegerField, and BigIntegerField. Why is this not in the same line of
thinking?
I might as well justify my use case a little more: I am building a
>
> Personally I do not see much need for it in core.
Same, it's not hard to implement as a custom field in a third party plugin.
Another point is that this isn't supported by SQLite - it only has "REAL"
meaning a double precision.
On 26 February 2017 at 16:21, Florian Apolloner
wrote:
> Pers
Personally I do not see much need for it in core.
> If I switched to single precision, I could cut the storage size of my
database in half with no loss of information.
Can you elaborate more on that? For it to be able to be usable you most
likely at least have also a serial field (which is anot
I have a Django project that uses the database to store a large number of
sensor readings. I use FloatField to store these, which maps to a double
precision float in the database. This is a waste of space, because the
sensors themselves are only accurately to a few decimal places. If I
switched
