Skip to content

Conversation

@orian
Copy link

@orian orian commented Jan 11, 2024

No description provided.

@johto
Copy link
Contributor

johto commented Jan 11, 2024

  1. Why do we want to remove this?
  2. Not arbitrarily chosen.

@orian
Copy link
Author

orian commented Feb 13, 2024

It caused me some problems and I would prefer the driver to stick to the database default (or at least document it).

Imho it should be like with default libs, if a user uses simple connector, it should use the default config, but it should also be possible to pass user specific config. I can provide simple proof-of-concept.

I've forked the lib and using my fork to not mess others people assumed behavior.

arp242 added a commit that referenced this pull request Jan 1, 2026
In PostgreSQL ≤11 the extra_float_digits parameter controlled how many
digits were used for floating point numbers. It was set here to ensure
people didn't accidentally needlessly lose precision (in 78a464e it was
set to 3. In 5941153 it was changed to 2 as people reported problems on
PostgreSQL ≤8.4, see #199).

Since PostgreSQL 12 it will always use maximum precision unless it's set
to ≤0. We only support PostgreSQL ≥14 now, so we can just remove it
here.

Ref: https://www.postgresql.org/docs/current/datatype-numeric.html#DATATYPE-FLOAT

Fixes #475
Fixes #1150
Fixes #1146
@arp242 arp242 closed this in 0f5c64d Jan 1, 2026
@arp242
Copy link
Collaborator

arp242 commented Jan 1, 2026

Fixed via #1212

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants