Ideas for improvements: drop the metadata node
----------------------------------------------
Key: MAGNOLIA-3051
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3051
Project: Magnolia
Issue Type: Improvement
Reporter: Fabrizio Giustina
Assignee: Boris Kraft
Just a thought for the future: the metadata node is there just to hold a few
properties that could better stay in the actual node. All the properties are
already prefixed by "mgnl:" so they can be filtered easily when needed. Why not
removing metadata nodes at all?
This will bring a bunch of small nice effects:
- reduce (to half) the number of nodes in the repository, improving
performances (now every time a node is read, also its metadata node is fetched).
- being able to sort properly on metadatas! A jcr query for sorting on the
creation date can be incredibly/unnecessary hard now (try getting all the nodes
with "a" in the title sorted by creation date... pretty evil)
- (minor) smaller/more readable xml files for bootstrap
We can easily keep APIs as they are now, since the MetaData class could just
fetch the same properties from the main node.
It will require a single-line change in the constructor, from:
{code}
this.node = workingNode.getNode(DEFAULT_META_NODE))
{code}
to:
{code}
this.node = workingNode;
{code}
I don't think metadatas are accessed directly in different ways, so updating
the APIs as described is probably enough. Redefining the nodetypes declaration
and adding a filter for xml import should complete the work.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
