Hi Ivan, Jorn,
I've run into similar requirements. A catch-all solution to this could
be to surface the ability to specify a custom deref procedure
define input:iri_deref DB.DBA.MY_CUSTOM_IRI_DEREF
This should get all the context to decide whether to perform a fetch
and also have access to the
Matthew Tedder wrote:
Ok..
Maybe I am seeing how it works now. I am not used to ODBC (usually, mysql,
postgresql, or mssql) and saw various examples under google searches
explicitly stating the database driver with such as driver=... in the odbc
connect statements.
Hi Matthew,
One PHP Dev
Aldo Bucchi wrote:
Hi Ivan, Jorn,
I've run into similar requirements. A catch-all solution to this could
be to surface the ability to specify a custom deref procedure
define input:iri_deref DB.DBA.MY_CUSTOM_IRI_DEREF
This should get all the context to decide whether to perform a fetch
and
On Tuesday 03 August 2010, Nathan wrote:
Aldo Bucchi wrote:
Hi Ivan, Jorn,
I've run into similar requirements. A catch-all solution to this could
be to surface the ability to specify a custom deref procedure
define input:iri_deref DB.DBA.MY_CUSTOM_IRI_DEREF
This should get all
Jörn Hees wrote:
On Tuesday 03 August 2010, Ivan Mikhailov wrote:
What should be added to existing extension API configurable via
define input:grab-resolver ...
and define input:grab-loader ...
as they're described in
http://docs.openlinksw.com/virtuoso/rdfiridereferencing.html#rdfinputgrab
Jörn Hees wrote:
On Tuesday 03 August 2010, Kingsley Idehen wrote:
[...]
Jörn Hees wrote:
If I use:
DEFINE get:proxy localhost:8890
with this query:
DEFINE input:grab-all yes
DEFINE input:grab-depth 1
SELECT DISTINCT ?p ?lp ?o ?lo
WHERE {
