[
https://issues.apache.org/jira/browse/VXQUERY-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779737#action_12779737
]
Vinayak Borkar commented on VXQUERY-16:
---------------------------------------
Good point. Let us break the Manipulator interfaces at the type boundaries.
The types like durations/datetime etc bother me too. Its a pain in the butt to
get right, and I am willing to make the assertion that there are a countable
few who would be willing to do so. We could get them to explore ways of
refactoring VXQuery to include their implementation.
I think we will need a "meet-in-the-middle" approach -- some types can be fully
externalized and some types will be translated into VXQuery's representation. I
think this is going to be an engineering decision.
Strings/Numbers are on one side and Datetimes/durations are on the other. The
hardest type to decide on is the QName -- Its common enough that you want a
really fast implementation, while not making too many assumptions about how it
is implemented -- That's the oxymoron.
> 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.
