[
https://issues.apache.org/jira/browse/VXQUERY-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779706#action_12779706
]
Till Westmann commented on VXQUERY-16:
--------------------------------------
One of the issues could be that the Manipulator interface gets quite big, if it
is the union of all AtomicValue sub-interfaces. So we might want to consider
breaking it up.
Another question would be how far the Manipulator interface would go. E.g.
today we have direct access to the Duration value of the DurationValue class
and we make some use of it to implement arithmetic operations efficiently.
One solution would be to provide a similar method on the Manipulator interface
and to implement the arithmetic operations for all DM implementations based on
the Duration values. But for a DM representation that does not use Duration
objects internally, it would be some evaluation overhead to create those.
Another solution would be to also move the arithmetic operations into the
manipulator interface, allowing for more efficiency, but also requiring more
implementation effort for each DM implementation.
> Externalize use of Name Cache
> -----------------------------
>
> Key: VXQUERY-16
> URL: https://issues.apache.org/jira/browse/VXQUERY-16
> Project: VXQuery
> Issue Type: Improvement
> Reporter: Vinayak Borkar
> Assignee: Vinayak Borkar
>
> QName management currently uses Name Caches. This needs to be externalized to
> the datamodel implementation. The core system should have a generic way of
> representing QNames
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
