Thanks. I'm now using pyodbc to connect to the ODBC interface, which works quite well.
peter On 9/6/18 5:49 AM, Hugh Williams wrote: > Hi Peter, > > You can get around this by using LIMIT / OFFSET in the query or by using one > of the SQL interfaces ie ODBC / JDBC / ADO.Net etc as was indicated in the > git issue (https://github.com/openlink/virtuoso-opensource/issues/700) and > even using our Jena/Sesame Provider which use JDBC under the covers for > connecting to Virtuoso ... > > Best Regards > Hugh Williams > Professional Services > OpenLink Software, Inc. // http://www.openlinksw.com/ > Weblog -- http://www.openlinksw.com/blogs/ > LinkedIn -- http://www.linkedin.com/company/openlink-software/ > Twitter -- http://twitter.com/OpenLink > Google+ -- http://plus.google.com/100570109519069333827/ > Facebook -- http://www.facebook.com/OpenLinkSoftware > Universal Data Access, Integration, and Management Technology Providers > > > >> On 6 Sep 2018, at 09:30, Peter F. Patel-Schneider <pfpschnei...@gmail.com> >> wrote: >> >> I had already bumped into the limit that you found. >> >> This is a second limit, also mentioned in that thread. This limit is >> 2^(24-3) >> for modern CPUs, as mentioned by iv-an-ru. It is this limit that I'm bumping >> into. Unfortunately, this limit appears to be something that can't be >> modified by simply changing a constant. >> >> I do not know just what this limit constrains. Can I get around it by using >> one of the other interfaces to Virtuoso? Can I get around it by using LIMIT >> and OFFSET? >> >> peter >> >> >> On 09/05/2018 08:19 PM, Daniel Hernandez wrote: >>> Peter, >>> >>> I have faced the same problem. It can be partially solved by modifying >>> the code of Virtuoso to remove the hardcoded limit. It implies recompiling >>> Virtuoso. This issue is commented here: >>> >>> https://github.com/openlink/virtuoso-opensource/issues/700 >>> >>> Daniel >>> >>> >>> ---- On Wed, 05 Sep 2018 21:30:01 -0300 Peter F. Patel-Schneider >>> <pfpschnei...@gmail.com> wrote ---- >>>> I'm trying to extract information from a large triple store and I'm >>>> running >>>> into Error SR078, which appears to be a hard limit on the number of rows >>>> in a >>>> result to 2^21 (for a 64 bit machine). I'm using the http interface and >>>> I've >>>> already increased the maximum number of http results to well more than >>>> 2^21. >>>> >>>> I was wondering if there was any way around this limit. Does it affect >>>> all >>>> results or can I use another interface to Virtuoso to get around the >>>> problem? >>>> Can I use LIMIT and OFFSET to get around the problem (although that would >>>> be a >>>> rather costly way to get around it)? >>>> >>>> peter >>>> >>>> ------------------------------------------------------------------------------ >>>> >>>> Check out the vibrant tech community on one of the world's most >>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >>>> _______________________________________________ >>>> Virtuoso-users mailing list >>>> Virtuoso-users@lists.sourceforge.net >>>> https://lists.sourceforge.net/lists/listinfo/virtuoso-users >>>> >>> >>> >> >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> Virtuoso-users mailing list >> Virtuoso-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/virtuoso-users > _______________________________________________ Virtuoso-users mailing list Virtuoso-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/virtuoso-users
