Home/ Questions/Q 268203
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T23:39:57+00:00

I try to store the PHP floating point value 63.59072952118762 into a double precision

  • 0

I try to store the PHP floating point value 63.59072952118762 into a double precision column in postgres. Postgres stores the value as 63.59073. Does anyone know why? 8 byte should be more than enough for that value. I’ve tried with the data type numeric, which works when specifying the precision, but that shouldn’t really be necessary.

Update: The same problem is present when trying to store 63.5907295, so the suggestion that something happens with the double before it’s getting stored seems realistic.

Update II (partly solved): The line where I assign the double parameter looks like this: 

$stmt->bindParam(4, $this->latitude);

The thing I didn’t know is that PDO defaults its param type to string. I changed it to PDO::PARAM INT in lack of a better alternative (PARAM DOUBLE was not an option), and got 10 digits precision in the double stored in postgres (some progress, at least). I’ve checked that the numeric type works well, so it seems that numeric is the way to go when using PDO and doubles that has to have a precision of more than 10 decimals.

Anyways, as someone has mentioned, I don’t know if it’s a must for me to have this kind of precision, but I think the problem in itself deserved to be investigated.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team
    • How do you determine what PostgreSQL is storing?
    • How do you send the data to PostgreSQL?
    • How do you get the data back again?
    • How do you display it?
    • What type is the column in the database?

    There are many, many places on the path between PHP and PostgreSQL where there could be confusion about how to represent the data.

    It is important to explain how data is inserted into the DBMS. Using a literal value in the INSERT statement leads to a different set of problems from using bound parameters. If you wrote the value out in the SQL:

    INSERT INTO SomeTable(SomeColumn) VALUES(63.xxxxxxxxx);

    and the data was truncated, you’d have a problem down in PostgreSQL. If you bind the variable, you have to be sure to understand what PHP and the PDO PostgresSQL modules do with the value – is it sent as a double, or as a string, and which code deals with the conversion, and so on.

    You run into analogous issues with Perl + DBI + DBD::YourDBMS (DBD::Pg in your case).

    • 0