[command] node:touch multivalue?

[dbu]

i just noticed that the touch command does not support multivalue properties. we might try to clean that up. have a --prop-add argument?

btw, is it possible to just change a property of an existing node or do we have to create a new node for that?

[dantleech]

In regard to modifying an existing node, yeah, touch will happily modify a node at the given path.

I wonder for prop-add if we can do some syntax like

--prop-set=foobar[]=bar
--prop-set=foobar["barfoo"]=foo

--prop-remove=foobar[0]
--prop-remove=foobar["barfoo"]

Actually - associative arrays are not supported in PHPCR-ODM .. right?

What would the syntax be for:

• Adding an element to the end of the stack?: --prop-add=foobar=bar | --prop-set=foobar[]=bar
• Replcaing an element at a specified index?: --prop-set=foobar[1]=bar
• Removing an element at a specified index?: --prop-remove=foobar[1]

[dbu]

i like this [] syntax, looks reasonble. and i prefer it over prop-add. prop-add is confusing as you might think you need to know if the property already exists and have no indication it has to do with multivalue.

associative arrays are supported by the ODM layer, but not by PHPCR natively, so we can only have numeric keys here. even in the doctrine bundle, the commands to modify a PHPCR node should not support associative arrays. on phpcr level its just 2 separate arrays, one for keys and one for values.

[dbu]

re our irc discussion, i think we should not add more property things into touch, but rather have phpcr:property:* commands for that. touching a node while creating a property at the same time has some value, but for full flexibility i would go with a separate command.

[dbu]

@dantleech is this still relevant? i guess the phpcr-shell can handle this a lot better and we should remove the node:touch standalone commands in favor of the shell.