No, not all metastrings. Just the orphaned ones that are not used anymore.
Thank's Juho.
I try to read gc plugin code and i find the query used to delete metastring that don't have metadatas and annotations.
SELECT * FROM {$CONFIG->dbprefix}metastrings WHERE
(
(id NOT IN (SELECT name_id FROM {$CONFIG->dbprefix}metadata)) AND
(id NOT IN (SELECT value_id FROM {$CONFIG->dbprefix}metadata)) AND
(id NOT IN (SELECT name_id FROM {$CONFIG->dbprefix}annotations)) AND
(id NOT IN (SELECT value_id FROM {$CONFIG->dbprefix}annotations))
)
Never,It will delete only those which does not have metadatas and annotations as said by @ Riadh Hamdi
please don't start duplicate threads, you've already asked this exact question a few days ago. If you need to ask followup questions continue it in that thread.
The answer is to either use different relationship names
Sorry matt, I think to expand the topic.
But the answer does not answer exactly the question. The current model can't implement a relation beetwwen more than two entities, In design,ie an associative table with more primary key has a cardinality of 0 .. n
Thank you
info@elgg.org
Security issues should be reported to security@elgg.org!
©2014 the Elgg Foundation
Elgg is a registered trademark of Thematic Networks.
Cover image by Raül Utrera is used under Creative Commons license.
Icons by Flaticon and FontAwesome.