-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Peter,
Indeed, Hugh seems to be confirming this now. I am however curious: how did you manage to get 'maxrows' working? Was your HTTP request similar to what I specified? I think my solution will be to use the TOP and LIMIT parameters to get all the results in multiple queries. Do you have any other ideas? Alex Peter Ansell wrote: > Hi Alex and Hugh, > > I put the maxrows in as a parameter in the same way as query and it did work > restrict the results to less than the 1000, but it did not allow me to select > more than 1000 even though I had both maxrows and the LIMIT set to more than > 1000. My impression from the original email about maxrows was that it could > be used to ask for more results than the hardcoded 1000 limit internally used > by the DBpedia endpoint but I guess that is not the case. > > Cheers, > > Peter > > > > ----- Original Message ---- >> From: Alex <alex...@gmail.com> >> To: Hugh Williams <hwilli...@openlinksw.com> >> Cc: Peter Ansell <p_ans...@yahoo.com>; virtuoso-users@lists.sourceforge.net >> Sent: Monday, 28 September, 2009 5:16:20 AM >> Subject: Re: [Virtuoso-users] Installing DBpedia datasets >> >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Hi Hugh, >> >> I've tried your suggestion of specifying the maxrows parameter, but >> don't seem to be seeing any difference using the DBpedia SPARQL endpoint >> (http://dbpedia.org/sparql). As far as I understand (the page isn't >> particularly clear on this), the parameter should be passed as an HTTP >> header. Perhaps I am mistaken on this? >> >> The following is a test SPARQL request I sent over HTTP: >> >> - ------------------------------------------------------------ >> >> POST /sparql HTTP/1.1 >> Content-Type: application/x-www-form-urlencoded >> maxrows: 500 >> Host: dbpedia.org >> Content-Length: 547 >> Connection: Keep-Alive >> >> query=%0d%0aPREFIX+skos%3a+%3chttp%3a%2f%2fwww.w3.org%2f2004%2f02%2fskos%2fcore%23%3e%0d%0aPREFIX+dbpedia%3a+%3chttp%3a%2f%2fdbpedia.org%2fresource%2f%3e%0d%0aPREFIX+dbpedia-cat%3a+%3chttp%3a%2f%2fdbpedia.org%2fresource%2fCategory%3a%3e%0d%0aPREFIX+dbpedia-owl%3a+%3chttp%3a%2f%2fdbpedia.org%2fontology%2f%3e%0d%0aPREFIX+foaf%3a+%3chttp%3a%2f%2fxmlns.com%2ffoaf%2f0.1%2f%3e%0d%0a%0d%0aSELECT+DISTINCT+%3farticle+%3fname+WHERE%0d%0a%7b%0d%0a++++%3farticle+a+dbpedia-owl%3aMilitaryConflict+.+%0d%0a++++%3farticle+foaf%3aname+%3fname+.%0d%0a%7d%0d%0a >> >> - ------------------------------------------------------------ >> >> Yet I am still receiving 1000 triples in response. Any ideas what could >> be going wrong here? >> >> Thanks, >> Alex >> >> Hugh Williams wrote: >>> Hi Peter, >>> >>> The current ResultSetMaxRows parameter in the Virtuoso configuration >>> file is 1000, restricting all SPARQL queries against the server to a >>> maximum of that size: >>> >>> http://docs.openlinksw.com/virtuoso/dbadm.html#ini_SPARQL >>> >>> This can be overridden by passing the "maxrows" sparql query option with >>> your query as detailed at: >>> >>> >> http://docs.openlinksw.com/virtuoso/rdfsparql.html#rdfsparqlprotocolendpoint > > > > __________________________________________________________________________________ > Get more done like never before with Yahoo!7 Mail. > Learn more: http://au.overview.mail.yahoo.com/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJKv/CAAAoJEOqaT4w4/2806gEH/AvhQ2CVf+WgbI+iDdQ0/0ej Z9JP064cpRxwbQhHJ0JuDZe2BgU7/C4R1q33s3PeKqFL/eX/7JikvMEBrjBgWqzk tJMW5tOeZ3/JQkYkdEXliRxc5nEGc5frQG3mB+n8pywNBL+g36w/jQmmndCdCABP I4hh8I2Bk3/LIYgyzFg+eV5wMPPp08Yn0D+we/4b+l2PAZwo9Vk1XRkKpTh8lFbV pqQPAdHeA0CdahGgOgw/vKpP/D4yARFMI664GHXJiXLBjXJnCq/kaVtBBaYIWy4q nbaVjMvMyOdPJGj2J+w3pgfC4W7Kpdvt9PB617MgKoK1zL3lfFEnjYlHTNq0Z4Q= =QAdF -----END PGP SIGNATURE-----
