Repository navigation
to_dataframe: an integer above 2**53 next to a float is rounded by pandas, the other readers keep it exact #340
Description
Found while writing the docs for the 26.11.1.post1 candidate (the docs branch read the code of #331 and checked the behaviour with pandas).
For a result column that holds an integer above 2**53 next to a floating point value, the readers of #331 keep the integer exact: to_columns() returns an exact Python list, and to_arrow() and to_polars() return a string column of the exact text. to_dataframe() is the exception: it hands the exact list to pandas, which infers float64 and rounds the integer. The same data therefore gives an exact value in three readers and a rounded one in the fourth.
Proposal: build such a column as an object Series in to_dataframe() (both wheels share the decoder, so the change is in one place), and add a test next to the 2**60 + 1 and 1.5 cases that #331 already has for to_columns() and to_arrow(). It is not part of 26.11.1.post1: that candidate is built and tested, and this changes a reader's output type for a rare shape. It goes into the next patch.
Activity
tae898 commentedon Nov 10, 2026
Fixed in the tag
26.11.1.post2(commit4d2db17).to_dataframe()now returns a result column that holds an integer beyond 253 next to a float as an object column of the same Python values, so the integer stays exact, as into_columns(). The tests sit next to the2**60 + 1and1.5cases of #331, and the same shape with the ends of int64 and a null. Integers alone stayint64, and integers up to 253 next to floats stayfloat64.On PyPI:
arcadedb-jvm 26.11.1.post2(4 wheels, first upload 2026-11-10 11:55 UTC) andarcadedb 26.11.1.post2(4 wheels, first upload 2026-11-10 12:25 UTC), none yanked. The published wheels pass the #340 case in a fresh environment.Left alone on purpose:
to_dataframe(convert_types=False)on the JVM wheel and its no-bridge fallback still round such a column, and an integer column with a null staysfloat64with NaN, which is the pandas rule. If you hit either, tell me here and I will open a follow-up.The fix is on
mainwith #351 (merge commit6619f13). I am closing this issue.Docs for post2: to_dataframe keeps an integer beyond 2**53 exact (#340)…
Docs for 26.11.1.post1 and post2: reading large results, columnar, pa…
to_dataframe: keep an integer beyond 2**53 next to a float exact (refs …
integration: merge fix/340-to-dataframe-int64-exact (4d2db17: to_data…
Merge the 26.11.1.post2 release line into main