Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong handling of graph in SPARQL-execution #22

Open
gfobe opened this issue Jun 14, 2012 · 0 comments
Open

Wrong handling of graph in SPARQL-execution #22

gfobe opened this issue Jun 14, 2012 · 0 comments

Comments

@gfobe
Copy link

gfobe commented Jun 14, 2012

In Erfurt_Store_Adapter_Virtuoso there are multiple issues when executing a sparql-query.

Erfurt_Store_Adapter_Virtuoso::_execSparql():
When $graphUri = null, in Virtuoso 06.01.3127 odbc_exec() rises an exception "Fatal error: Out of memory (allocated 10485760) (tried to allocate 18446744073709551613 bytes)" (nearly 2^64 on 64bit-system). This is, because Virtuoso comes in trouble (also in ISQL console) when a graph named 'NULL' passed to DB.DBA.SPARQL_EVAL(). So it's only possible to quote the graph name when it's not null, otherwise real NULL must be passed as this parameter to virtuoso.

Erfurt_Store_Adapter_Virtuoso::_execSparqlUpdate():
Here we also have the param $graphUri, also used nowhere in the class like in Erfurt_Store_Adapter_Virtuoso::_execSparql(). The default graph definition is created in $graphSpec, but not in use. Is it possible to add a comment why to use DB.DBA.SPARQL_EVAL in _execSparql(), but a simple SPARQL in _execSparqlUpdate()? Furthermore the PHPDoc is missing for this method.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant