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
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
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
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
