Thetype exposes the following members.
Discards any outstanding changes.
Determines whether the specified object is equal to the current object.(Inherited from Object.)
Allows an object to try to free resources and perform other cleanup operations before it is reclaimed by garbage collection.(Inherited from Object.)
Flushes any outstanding changes to the underlying store.
Serves as the default hash function.(Inherited from Object.)
Gets the Type of the current instance.(Inherited from Object.)
Creates a shallow copy of the current Object.(Inherited from Object.)
Processes an ADD command.
Processes a CLEAR command.
Processes a command.
Processes a command set.
Processes a COPY command.
Processes a CREATE command.
Processes a DELETE command.
Processes a DELETE DATA command.
Processes a DROP command.
Processes an INSERT command.
Processes an INSERT DATA command.
Processes a LOAD command.
Processes an INSERT/DELETE command.
Processes a MOVE command.
Returns a string that represents the current object.(Inherited from Object.)
If the provided manager also implements the IUpdateableStorage interface then the managers native SPARQL Update implementation will be used for the non-type specific calls i.e. ProcessCommand() and ProcessCommandSet(). At all other times the SPARQL Update commands will be processed by approximating their behaviour through calls to SaveGraph(), LoadGraph() and UpdateGraph() in addition to local in-memory manipulation of the data. Some commands such as INSERT and DELETE can only be processed when the manager is also a IQueryableStorage since they rely on making a query and performing actions based on the results of that query.
The performance of this processor is somewhat dependent on the underlying IStorageProvider. If the underlying manager supports triple level updates as indicated by the UpdateSupported property then operations can be performed quite efficiently, if this is not the case then any operation which modifies a Graph will need to load the existing Graph from the store, make the modifications locally in-memory and then save the resulting Graph back to the Store.