[
https://issues.apache.org/jira/browse/JENA-721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Vesse updated JENA-721:
---------------------------
Issue Type: Improvement (was: Bug)
This functionality is by design - see the [TDB Value
Canonicalization|https://jena.apache.org/documentation/tdb/value_canonicalization.html]
documentation - so I am changing this to an Improvement rather than a Bug
There are no plans to increase the range of inlined types or to change the
canonicalisation behaviour at this time.
Contributions which improve this are of course welcome
Any change in this area would be a breaking change to the TDB disk format and
TDB query/update evaluation so would need careful consideration
> Inline literals, source types are discarded
> -------------------------------------------
>
> Key: JENA-721
> URL: https://issues.apache.org/jira/browse/JENA-721
> Project: Apache Jena
> Issue Type: Improvement
> Components: TDB
> Affects Versions: TDB 1.0.1
> Reporter: Marek Kowalczyk
>
> NodeId.inline$ changes the actual type of literals from subtypes of
> xsd:integer to xsd:integer, for instance: literals of type
> xsd:positiveInteger are stored ad inline type INTEGER and during read decoded
> as xsd:integer in NodeId.extract(NodeId)
> {code}
> case INTEGER:
> {
> long val = IntegerNode.unpack(v) ;
> Node n = NodeFactory.createLiteral(Long.toString(val), null,
> XSDDatatype.XSDinteger) ;
> return n ;
> }
> {code}
> It would be nice to add support for various xsd:types and use the 7 bits
> reserved for inline type to represent more than 7 types.
> As a fastest workaround I've disabled the inline literals in NodeId( using
> reflection) , but it would be great If it would be configurable via context
> or parameter in StoreConnection.make(); or via SystemParams
--
This message was sent by Atlassian JIRA
(v6.2#6252)
