[MGNLDATA-121] Add support for multi-valued properties Created: 04/May/11  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia Data Module (closed)
Component/s: None
Affects Version/s: 1.6.2
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Teresa Miyar Assignee: Philipp Bärfuss
Resolution: Won't Do Votes: 6
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

One use case would be to be able to use categories (as per the categorization module) to categorize other data items.



 Comments   
Comment by Teresa Miyar [ 15/Jun/11 ]

2 possible solutions:
We could make the RegisterNodeTypeTask able to register types with property multiple set to true. Only this types will accept multiple values. What happens on existing types? In my opinion they are not using multiple and if they want to do it they must be updated by users.

We could update the NodeType dataItem to have the property multiple set to true. All types will accept multiple values. That could affect to user queries&code as in jcr specification says: "a multi-value property can have no values (i.e., be an empty array), whereas a single-value property either has a (non-null) value or does not exist."

Comment by Sean McMains [ 20/Jun/11 ]

I would lean toward the latter, myself. Troubleshooting seems like it gets more difficult if we don't know, for a given version of the data module, whether multi-value properties are enabled or not. Additionally, the difference between an empty array (for multi-value properties) and not existing (single-value properties) seems small and easily worked around. (Though, admittedly, making a change that may break existing code doesn't seem like the sort of thing that should go into a maintenance release.)

Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 05:11:33 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.