Hi Mark,
An iODBC Driver Manager trace would be useful to have to see where the fails
are occurring with the EasySoft ODBC driver. We have not performed any testing
of Virtuoso with the EasySoft ODBC driver and thus would recommend the use of
the OpenLink Multi-Tier ODBC Drivers, which have
Hi Patrick,
I followed your recommandation, still having the same issue.
I had the message:
Invalid command 'ProxyHTMLEnable' when restarting apache.
In fact, it seems to be related to my problem, as response from html server
systematically removed /virtuoso/.
After investigating on the web, I
Going further on investigation, I've some little problems:
1- strange caracters appearing on the conductor screen (A like symbol on
capture of virtuoso conductor screen)
2- with isparql, it seems that some stylesheet does not apply (can be
compared between the two ispaql captures attached)
Any
Hi Nicolas,
I followed your recommandation, still having the same issue.
I had the message:
Invalid command 'ProxyHTMLEnable' when restarting apache.
In fact, it seems to be related to my problem, as response from html
server systematically removed /virtuoso/.
This module may not be
HI Nicolas,
Going further on investigation, I've some little problems:
1- strange caracters appearing on the conductor screen (A like
symbol on capture of virtuoso conductor screen)
Will need to have a look using your method of proxy rewrite to see
what it produces. I did not notice
I decided to use CONSTRUCT to make a new predicate with the search terms,
that can be inserted with SPARUL.
In case anyone's interested,
example for albums that can be looked up by artist and/or album name. It
seems to work ok with
CONSTRUCT {
?s http://localhost/literals `bif:concat(?o, ,
While trying to get to the bottom of a very very slow query I notives this:
$ nepomukcmd query select count(distinct ?r) where { ?r a ?t . \
?t rdfs:subClassOf rdfs:Resource . \
?r ?p ?o . \
?o bif:contains 'nepo' . \
}
$ callret-0 -
Hi Hugh,
Thanks for following up on this.
Is there a possibility of getting new functionality to handle this in
future?
My thinking is
1. Allow the tweaking of the mapping between virtuoso and the other
database to be able to explode the data. Perhaps using sql? Or alternatively
-
