[PHPCR-36] Provide migrations tool Created: 17/Nov/11  Updated: 28/Feb/14  Resolved: 28/Feb/14

Status: Closed
Project: Doctrine PHPCR
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: New Feature Priority: Minor
Reporter: David Buchmann Assignee: Jordi Boggiano
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Reference
relates to PHPCR-7 add support for "eventual migrations" Resolved

 Description   

when i have existing content and later change the document class to have referenceable=true, this is not updated even on persisting the document again.

uwe: I think there are several other things that fail when you have existing content in the repository - maybe the solution to think about is something like migrations ... that would prevent the performance penalty on ordinary code and still give you the change to change the structure of your documents.

things that come to mind

  • change document class name
  • removing fields
  • change field type
  • bulk changing the values in some field
  • everything related to node types (though, as an additional challenge at least jackrabbit does not allow to remove things from node types through the davex remoting we use in jackalope)


 Comments   
Comment by David Buchmann [ 28/Feb/14 ]

we now have commands to do such things.

Generated at Wed Aug 27 21:15:03 UTC 2014 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.