Add PropertyTypeFinder (smwgFixedProperties)

[mwjames]

This PR is made in reference to: SemanticMediaWiki/semantic-mediawiki.org#14

This PR addresses or contains:

• Simplify $smwgFixedProperties customizing where the type is now read from the property instead of having it declared as customizing which would create issues when the type on the property page and the $smwgFixedProperties setting are different from each other
• Table name is no longer the complete md5 hash instead substr( base_convert( md5( $tableName ), 16, 32 ), 0, 12 ) is used to get a shorter ID
• Property page now displays a message that any change to its type requires some admin activity

$GLOBALS['smwgFixedProperties'] = array(
	'Has fixed test'
);

This PR includes:

• Tests (unit/integration)
• CI build passed

[mwjames]

@kghbln FYI

[kghbln]

How awesome is this???!!! Great and many thanks!!! Just documented.

What about RDF stores? Will this work for them too? I suppose so.

[kghbln]

This is a highlight thus 7f3fe52

[mwjames]

This is a highlight thus 7f3fe52

At first, I just wanted to scratch an itch where a DataItem object reference would appear in the LocalSettings and I ended up fixing the whole "Fixed Properties" issue.

Property names must use underscores and not spaces or you will see MWException errors on some page actions.

Properties without an underscore do no longer cause a MWException, meaning that Has_fixed_text and Has fixed text will be handled as equivalent [0].

What about RDF stores? Will this work for them too? I suppose so.

This issue relates to the creation of extra DB tables with a RDF store not being linked to internal changes of the SQLStore therefore declaring properties as fixed table properties will have no effect on the SPARQLStore or for that matter to the RDF export.

[0] https://github.com/SemanticMediaWiki/SemanticMediaWiki/pull/2135/files#diff-53920baeff0ad9c3bad870946bb97034R221

[kghbln]

Properties without an underscore do no longer cause a MWException, meaning that Has_fixed_text and Has fixed text will be handled as equivalent [0].

Good to know that there are less worries. :)

This issue relates to the creation of extra DB tables with a RDF store not being linked to internal changes of the SQLStore therefore declaring properties as fixed table properties will have no effect on the SPARQLStore or for that matter to the RDF export.

Thanks a lot for this info. I guess me having a better understanding of RDF store will be preferable in future.