SPARQLUpdateStore writes an HTTP transaction for each and every triple addition or deletion. When adding significant amounts of data via this API, this results in a lot of network chatter and significant delays while the transactions are completed. This change batches edits up until the user calls commit() or until a read operation is performed. The result should always be the same behavior from any given client's perspective, since all edits are applied before a read occurs.
SPARQLUpdateStore writes an HTTP transaction for each and every triple addition or deletion. When adding significant amounts of data via this API, this results in a lot of network chatter and significant delays while the transactions are completed. This change batches edits up until the user calls commit() or until a read operation is performed. The result should always be the same behavior from any given client's perspective, since all edits are applied before a read occurs.

ssssam/rdflib,ssssam/rdflib,dbs/rdflib,avorio/rdflib,marma/rdflib,dbs/rdflib,marma/rdflib,RDFLib/rdflib,dbs/rdflib,avorio/rdflib,RDFLib/rdflib,avorio/rdflib,avorio/rdflib,ssssam/rdflib,dbs/rdflib,marma/rdflib,RDFLib/rdflib,marma/rdflib,RDFLib/rdflib,ssssam/rdflib