(Bug 59204) Properties do not unset on page deletion

Clean-up of related subjects to a property has to be done before store data
are modified which means that either run UpdateDispatcherJob before the
deleteSubject() in "online" mode or put both UpdateDispatcherJob and deleteSubject()
in a DeferredSubjectRemovalJob to ensure synchronize execution.
SQlite no such table: unittest_unittest

$db->tableName( $proptable->getName() ) returns unittest_unittest on SQLite
which causes test to fail.

https://s3.amazonaws.com/archive.travis-ci.org/jobs/16315316/log.txt
Fix double prefixing issue in SMWSQLStore3Readers::getProperties

This method really should be its own class. Also not sure why this
just happened for sqlite. Perhaps the affected branch of the if is
just generally broken and another bug that is sqlite specific caused
it to be executed for sqlite?
Merge pull request #73 from SemanticMediaWiki/bugfix

Fix double prefixing issue in SMWSQLStore3Readers::getProperties
(Bug 59204) Properties do not unset on page deletion

Clean-up of related subjects to a property has to be done before store data
are modified which means that either run UpdateDispatcherJob before the
deleteSubject() in "online" mode or put both UpdateDispatcherJob and deleteSubject()
in a DeferredSubjectRemovalJob to ensure synchronize execution.
SQlite no such table: unittest_unittest

$db->tableName( $proptable->getName() ) returns unittest_unittest on SQLite
which causes test to fail.

https://s3.amazonaws.com/archive.travis-ci.org/jobs/16315316/log.txt
Fix double prefixing issue in SMWSQLStore3Readers::getProperties

This method really should be its own class. Also not sure why this
just happened for sqlite. Perhaps the affected branch of the if is
just generally broken and another bug that is sqlite specific caused
it to be executed for sqlite?
Merge branch 'bug' of github.com:SemanticMediaWiki/SemanticMediaWiki into bug
Increment to 1.9.0.1
Add DeleteSubjectJob to allow to schedule a DeferredJob

CRAP: 14
CC: 100%

The removal of a subject from the Store is being moved into a
`DeleteSubjectJob` and if necessary can be scheduled as `DeferredJob`
(enables to run deletion as background job).

Prior SMW 1.9, the subject deletion did not initiate any clean-up of
possible associate subjects, the
`smwgDeleteSubjectWithAssociatesRefresh` setting will allow to refresh
entities that are connected to a deleted subject.

A subject may be connected to a large group of associates, it is therefore
advisable that `smwgDeleteSubjectAsDeferredJob` is set TRUE in order to
avoid any performance issues (or runtime errors) during the deletion process.

In case the deletion is executed as `DeferredJob` it is suggested that
the JobQueue is being run repeatedly within a narrow time frame to avoid
an increased backlog.

### Legacy (default) setting
$GLOBALS['smwgOnDeleteAction'] = array(
	'smwgDeleteSubjectAsDeferredJob' => false,
	'smwgDeleteSubjectWithAssociatesRefresh' => false
);
Merge branch 'r1901' of git@github.com:SemanticMediaWiki/SemanticMediaWiki.git into bug
Merge pull request #71 from SemanticMediaWiki/bug

(Bug 59204) Properties do not unset on page deletion