Hi Hugh.
Is there any ETA for the bug fix?
Br
Timo Westkämper
On 05/08/2011 01:41 AM, Hugh Williams wrote:
Hi Timo,
This is logged on our internal bugzilla system which external users do
not have access to ...
Best Regards
Hugh Williams
Professional Services
OpenLink Software
Web: http
correctly, the problem is
that I don't want any SQL types, since they don't have the timezone
offset preserved.
Trying different output:valmode options didn't help.
Br,
Timo Westkämper
On 05/06/2011 02:38 PM, Hugh Williams wrote:
Hi Timo,
Yes you can access SPARQL results se
Hi Hugh.
Could you send me a link to the ticket? Thanks.
Br,
Timo Westkämper
On 05/06/2011 02:48 PM, Hugh Williams wrote:
Hi Timo,
This problem and been recreated and reported to development for
resolution ...
Best Regards
Hugh Williams
Professional Services
OpenLink Software
Web: http
<http://test> ?p ?o }
The results are :
http://test12000-01-01T00:00:00Z
http://test22000-01-01T00:00:00+02:00
I am having the same issue when using SPARQL via JDBC. The timezone
offset is ignored when using SPARQL via JDBC or the Interactive SQL form.
Br,
Timo Westkämper
the literal via the java.sql.Timestamp instance,
it is not possible.
Br,
Timo Westkämper
Hi.
Got the issue fixed myself. It was a java.sql.Date issue. Sorry for the
noise.
Br,
Timo Westkämper
On 05/03/2011 02:50 PM, Timo Westkämper wrote:
Hi.
As an update to the previous issue, xsd:dateTime literals work correctly.
Br,
Timo Westkämper
On 05/03/2011 12:00 PM, Timo Westkämper
Hi.
As an update to the previous issue, xsd:dateTime literals work correctly.
Br,
Timo Westkämper
On 05/03/2011 12:00 PM, Timo Westkämper wrote:
Hi.
I am having issues with RDF date literal persistence.
Dates after 1900-01-01 are persisted correctly, but 1900-01-01 and
before are shifted
Hi.
I am having issues with RDF date literal persistence.
Dates after 1900-01-01 are persisted correctly, but 1900-01-01 and
before are shifted one day into the past.
e.g.
"1900-01-01"^^xsd:date is transformed into "1899-12-31"^^xsd:date
What am I doing wrong? Or is t
SELECT * WHERE { `iri(??)` `iri(??)` ?o } with the related bindings,
does the PSOG index (or equivalent) get used in both cases?
Br,
Timo Westkämper
On 03/29/2011 08:03 AM, Ivan Mikhailov wrote:
Hello Timo,
When parameter values are placed right into the text of the query, the
compiler has a
got any special indexes configured.
Br,
Timo Westkämper
Best Regards
Hugh Williams
Professional Services
OpenLink Software
Web: http://www.openlinksw.com
Support: http://support.openlinksw.com
Forums: http://boards.openlinksw.com/support
Twitter: http://twitter.com/OpenLink
On 28 Mar 2011,
for SPARQL cause these issues or maybe
something else?
Br,
Timo Westkämper
On 03/28/2011 12:20 PM, Hugh Williams wrote:
Hi Timo,
Can you please provide more details on this issue possibly with some pseudo
code to demonstrate what is being done ? Are you getting the expected
performance
Hi.
I have noticed that when using SPARQL over JDBC as prepared statements I
get a huge performance penalty when binding variables acting as
predicates via prepared statements.
I'd like to bind all node constants via prepared statements. How can I
avoid the performance penalty?
Br,
Hi Ivan.
Thanks for the explanation.
Br,
Timo Westkämper
On 03/08/2011 05:25 PM, Ivan Mikhailov wrote:
Hello Timo,
On Mon, 2011-03-07 at 14:29 +0200, Timo Westkämper wrote:
Hi all.
How do I correctly bind the named graph context of the following SPARQL
query :
CONSTRUCT { ?s ?p ?o
}
Both throw Exceptions.
What is the right way to do it?
I am aware that it works also as
CONSTRUCT { ?s ?p ?o} WHERE { graph ?context { ?s ?p ?o } }
but I prefer the syntax form using FROM.
Br,
Timo Westkämper
Hello Ivan.
Thanks for the suggestion. That fixed the query. I was so confused by
the error message that I didn't check the query properly ;)
Br,
Timo Westkämper
On 02/24/2011 09:43 PM, Ivan Mikhailov wrote:
Hello Timo,
I'm not an JDBC maintainer, but inequal
Hi.
I am having troubles using CONSTRUCT queries with PreparedStatements.
e.g.
sparql define output:format '_JAVA_'
CONSTRUCT { ?s ?p ?o }
WHERE
{ `iri(??)` ?p ?o }
LIMIT 1
throws
Caused by: virtuoso.jdbc4.VirtuosoException: Index 1 is not 1
Hello Ivan.
Thanks for the detailed answer. I will then do the ordering afterwards.
Br,
Timo Westkämper
Hello Timo,
It is not ignored when bindings are sorted to get proper "cut" via LIMIT
and OFFSET. However the triples made according to variable values from
that bindings form
Hi.
Is the ORDER BY part of SPARQL Construct queries ignored? It seems so
when using Virtuoso via JDBC.
Br,
Timo Westkämper
don't want to construct SPARQL queries with String concatenation, as
this enables code injection attacks etc without proper escaping.
Br,
Timo Westkämper
context? Can I get significant benefits when grouping multiple
triples into one prepared statement pattern?
I am asking these directions beforehand, because there are lots of
directions for performance testing.
Br,
Timo Westkämper
Hi Hugh.
The update fixed the issue. Thanks.
Br,
Timo Westkämper
Hi Timo,
What is the version of the Virtuoso Sesame Provider you are using, run the
command:
java -jar virt_sesame2.jar
If you are running a Virtuoso open source build from before the last July 2010
6.12 release
", RDFS.LABEL);
The effective SPARQL query should be something like "select ?s ?p ?o
where { ?s ?p ?o. FILTER (?p == rdfs:label ) . } limit 5", but Virtuoso
uses the raw query without the bindings.
Any chance to get a fix for this?
Br,
Timo Westkämper
virt_sesame3.jar
Failed to load Main-Class manifest attribute from
virt_sesame3.jar
The CVS version works, the other one doesn't.
Br,
Timo Westkämper
Hi Timo,
I don't get it, as you say the initial download was from
http://virtuoso.openlinksw.com/dataspace/dav/wiki/Main/VOSDownloa
Hi Hugh.
The jar in CVS (virt_sesame3.jar) works perfectly well, and the sources
seem fine as well, but the jar on the Download page causes the Exception.
It seems that for some reason the used ValueFactory doesn't contain a
BNodeFactory.
Best regards,
Timo Westkämper.
Hi Timo,
sources for the Virtuoso Sesame 3 adapter available for
download? This way I could debug the problem more easily.
Best regards
Timo Westkämper.
Hi Timo,
Yes, Virtuoso does support blank nodes as does the Virtuoso Sesame Provider.
How exactly are you compiling and attempting to run the application
ortedOperationException
at
org.openrdf.model.impl.ValueFactoryImpl.createBNode(ValueFactoryImpl.java:86)
...
Blank nodes are not supported with OpenLink Virtuoso?
Best regards
Timo Westkämper
26 matches
Mail list logo
