My boss says that it's better to save a float value as TEXT instead of "double precision" type because he doesn't want to lose precision when the data is extracted from de BD and put it into an API response. The flow will be something like this: Postgresql -> Ruby -> JS -> API. The values are geographical coordinates.
Ask HN: Best data type to save coordinates with relative accurate precision?
1–1 of 1 posts