[
https://issues.apache.org/jira/browse/CLEREZZA-865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13885172#comment-13885172
]
Enrico Daga commented on CLEREZZA-865:
--------------------------------------
In that method we generate a new blank node skolem id in Virtuoso before we
insert data. This is needed to make subsequent insertion of triples to refer to
bnodes consistently.
So the usage of the string representation of the bnode is only needed to fetch
back the triple (before we delete it). You are right, being a temporary triple
we can use any uniq string instead (maybe the bnode.toString + random should be
enough, or a uuid if we want to be elegant...). I will change that.
Said that, all this turnaround should be replaced with a more "native" method
of generating a new bnode id in virtuoso, invoking a dedicated procedure would
be the ideal, but I couldn't found anything enough safe by now, so we live with
this for the moment.
> VirtuosoMGraph does not serialize bnodes correctly in internal queries
> ----------------------------------------------------------------------
>
> Key: CLEREZZA-865
> URL: https://issues.apache.org/jira/browse/CLEREZZA-865
> Project: Clerezza
> Issue Type: Bug
> Reporter: Enrico Daga
> Assignee: Enrico Daga
>
> For this reason performFilter throws an exception when a bnode that is
> returned by a previous read operation is then used as parameter of a new read.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
