id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
32118	db.models.FloatField name misleading	Michael	nobody	"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`, 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?

PostgresQL calls 4 byte float a `real`, and a 8 byte float a `double precision`:
https://www.postgresql.org/docs/9.1/datatype-numeric.html

Mysql calls 4 byte float a `float`, and a 8 byte float a `double`:
https://dev.mysql.com/doc/refman/8.0/en/floating-point-types.html

Note: People cite ""space is cheap"", but this is not always the case, and depending on the situation there are real practical savings."	New feature	new	Database layer (models, ORM)	3.1	Normal		Fields		Unreviewed	0	0	0	0	0	0