Robo 3T 1.1 - Big float numbers are showing incorrectly #1447
Comments
I am experiencing the same issue. As a result, the "Copy JSON" output is not considered valid for "Insert Document" which makes it difficult to move data from one collection to another. As a workaround the following regular expression can be used on the output of copy JSON: find: |
Hi @jimblind, @patrick-webs, thanks for reporting the problem. @patrick-webs |
Hi @simsekgokhan I think the problem I had was the exact same as reported by @jimblind , which is that when I do "Copy JSON" in Robo 3T I get a result like this:
note the value for the "a" key is not accepted as a valid JSON value for inserting back using the Insert Document feature of Robo 3T. |
Update: Next Actions
Details:
|
…oblems, incorrect value representation for 15 digit precision, -Infinity problem.
Update: Next Actions
Details:
|
@simsekgokhan Any news on this? |
https://blog.robomongo.org/robo-3t-1-2/ This blog post says it is fixed, but the issue is still open? |
@arboleya , @lacivert Can you guys share if you have any problems? |
FWIW, I think the issues I was having have been resolved in Robo 3T 1.2, my data set now properly outputs like
which is valid for insert. I think the issue is still open due to what was mentioned above "Remaining problems after the latest commit" |
In Robomongo 0.8.5 using query "db.getCollection('collectionname').find({})" got results:
We use float number type for IDs - in 0.8.5 version such numbers looks OK
In Robo 3T 1.1 for the same query results are:
Please help to get proper values for big float numbers in Robo 3T 1.1.
The text was updated successfully, but these errors were encountered: