version_numified should be string, not number about metacpan-client HOT 5 CLOSED

Hm... maybe this is a non-issue. I just saw that $s = "4.5"; p $s will print 4.5 (without quotes)

from metacpan-client.

The entire point of the field is to store it as a number and allow numeric operations. We aren't losing any precision by not representing it as a string.

from metacpan-client.

perl cannot correctly compare 1.000000000000000000001 with 1.000000000000000000002 numerically. That's why I say we lose precision if we get numbers back for this field.

On the other hand if perl is handed those values as strings and inserts them in a mysql database field of type DECIMAL(42,21), then mysql can compare those numbers, sort them, or whatever, with no precision lost.

Does anyone lose anything if these values are strings?

from metacpan-client.

You lose the ability to perform numeric comparisons on it in elasticsearch, which is the entire reason for the field's existence.

PAUSE already limits version numbers to 16 characters long.

from metacpan-client.

this is not a client issue, as explained by @haarg this ES mapping of the field as 'float'.

from metacpan-client.