fragment_downloaded_cb({"url":"tracker-sparql-connection.html#trackersparqlconnection-page","fragment":"TrackerSparqlConnection\nTrackerSparqlConnection is an object that represents a connection to a\nSPARQL triple store. This store may be local and private (see\ntracker_sparql_connection_new), or it may be a remote connection to a\npublic endpoint (See tracker_sparql_connection_bus_new and\ntracker_sparql_connection_remote_new).\nA TrackerSparqlConnection is private to the calling process, it can be\nexposed publicly via a TrackerEndpoint, see tracker_endpoint_dbus_new.\nUpdates on a connection are performed via the tracker_sparql_connection_update\nfamily of calls. tracker_sparql_connection_update_array may be used for batched\nupdates. All functions have asynchronous variants.\nQueries on a connection are performed via tracker_sparql_connection_query\nand tracker_sparql_connection_query_statement. The first call receives a\nquery string and returns a TrackerSparqlCursor to iterate the results. The\nsecond call returns a TrackerSparqlStatement object that may be reused for\nrepeatable queries with variable parameters. tracker_sparql_statement_execute\nwill returns a TrackerSparqlCursor.\nDepending on the ontology definition, TrackerSparqlConnection may emit\nnotifications whenever changes happen in the stored data. These notifications\ncan be processed via a TrackerNotifier obtained with\ntracker_sparql_connection_create_notifier.\nAfter use, a TrackerSparqlConnection should be closed. See\ntracker_sparql_connection_close and tracker_sparql_connection_close_async.\nA TrackerSparqlConnection may be used from multiple threads, asynchronous\ndatabase updates are executed sequentially on arrival order, asynchronous\nqueries are executed in a thread pool.\n"});