Closed code-shoily closed 1 month ago
I was running a query the had results as bigints. The table cells rendered fine. But as I copied the number, I saw the last two digits were 00.
00
To make a reproduction easier, I have stripped my query and it is now:
a_number = 387_794_919_168_006_419 Ecto.Adapters.SQL.query!( Repo, "SELECT $1::bigint", [a_number] )
The result should have been 387_794_919_168_006_419 but when I copy/paste it, it becomes 387_794_919_168_006_400
387_794_919_168_006_419
387_794_919_168_006_400
(The ,-s were slightly annoying but that's fine I guess, or maybe I could turn it off but I didn't know about it)
,
I am attaching screenshots below:
My bad. I was using an older version of kino_db. Closing this with apologies.
kino_db
I was running a query the had results as bigints. The table cells rendered fine. But as I copied the number, I saw the last two digits were
00
.To make a reproduction easier, I have stripped my query and it is now:
The result should have been
387_794_919_168_006_419
but when I copy/paste it, it becomes387_794_919_168_006_400
(The
,
-s were slightly annoying but that's fine I guess, or maybe I could turn it off but I didn't know about it)I am attaching screenshots below:
The rendered table (This is fine)
As I double clicked the cell to copy it