Issue handling xsd:double and xsd:decimal #114

Open
jakubklimek opened this Issue Dec 9, 2013 · 3 comments

Comments

Projects
None yet
4 participants
@jakubklimek

In develop/6, I have issue with loading xsd:double and xsd:decimal datatypes.
When I load "50.08332824707031"^^xsd:double using SPARQL update, when I look at the value using fct or simply by querying, I get "50.0833"^^xsd:double. However, if I load it as "50.08332824707031"^^xsd:decimal, I get "50.08332824707031"^^xsd:double.

I think both cases are wrong. The second one has the effect that when I dump the graph and load it again, it goes through case 1) loosing precision.

@HughWilliams

This comment has been minimized.

Show comment Hide comment
@HughWilliams

HughWilliams Dec 15, 2013

Collaborator

I have asked development to look into this and will let you know what they report back ...

Collaborator

HughWilliams commented Dec 15, 2013

I have asked development to look into this and will let you know what they report back ...

@jindrichmynarz

This comment has been minimized.

Show comment Hide comment
@jindrichmynarz

jindrichmynarz Apr 3, 2017

Was there any progress on this? While xsd:decimal should be lossless, Virtuoso implements it as lossy. Observe:

SELECT ?value
WHERE {
  VALUES ?value {
    0.00262335315960871
  }
}

When provided with 0.00262335315960871 Virtuoso returns 0.002623353159609.

Tested on Virtuoso 07.20.3218.

Was there any progress on this? While xsd:decimal should be lossless, Virtuoso implements it as lossy. Observe:

SELECT ?value
WHERE {
  VALUES ?value {
    0.00262335315960871
  }
}

When provided with 0.00262335315960871 Virtuoso returns 0.002623353159609.

Tested on Virtuoso 07.20.3218.

@HughWilliams

This comment has been minimized.

Show comment Hide comment
@HughWilliams

HughWilliams Apr 22, 2017

Collaborator

I have reported to development to look into ...

Collaborator

HughWilliams commented Apr 22, 2017

I have reported to development to look into ...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment