[
https://issues.apache.org/jira/browse/JENA-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Laurent Pellegrino updated JENA-69:
-----------------------------------
Attachment: JENA-69-r1128283.patch
A new patch that uses RIOT. The three old patches can be ignored.
I have added a asInt() method into the Token class because the Token class
detects that we have an integer but does not contain any method to retrieve the
value (the asWord method check the type and returns the value only if the type
is KEYWORD).
Regarding the Token class why are you using the type and switch/case
anti-pattern. I mean it would nice to use an Abstract Token class and one class
for each Token type (e.g. one for KeywordToken, one for IntegerToken, etc.) and
then you expose the methods that are specific to a class into this class. Thus,
you don't have to perform any type check as in the asX() methods, etc. because
all is done at compile time. Is there a performance issue to avoid that?
> Provide TSVInput reader
> -----------------------
>
> Key: JENA-69
> URL: https://issues.apache.org/jira/browse/JENA-69
> Project: Jena
> Issue Type: New Feature
> Components: ARQ, TDB
> Reporter: Laurent Pellegrino
> Priority: Blocker
> Labels: arq, resultset, tdb, tsv, tsvinput
> Attachments: JENA-69-r1128283.patch,
> removenodeclib-r1128186-version1.patch, tsvinput-r1128173-version1.patch,
> tsvinput-r1128173-version2.patch
>
>
> As stated into the mailing-list it is possible to serialize a ResultSet by
> using the TSV format. However, it is not possible to unserialize it (there is
> no TSVInput implementation).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
