Details
-
Type:
New Feature
-
Status:
Open
-
Priority:
Minor
-
Resolution: Unresolved
-
Labels:None
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)
Issue Links
- relates to
-
PHPCR-7
add support for "eventual migrations"
-
Activity
David Buchmann
made changes -
| Field | Original Value | New Value |
|---|---|---|
| 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 * 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) |
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) |
Lukas Kahwe
made changes -
| Priority | Major [ 3 ] | Minor [ 4 ] |
Lukas Kahwe
made changes -
This list may be incomplete, as errors occurred whilst retrieving source from linked applications:
- Request to http://www.doctrine-project.org/fisheye/ failed: Error in remote call to 'FishEye 0 (http://www.doctrine-project.org/fisheye/)' (http://www.doctrine-project.org/fisheye) [AbstractRestCommand{path='/rest-service-fe/search-v1/crossRepositoryQuery', params={query=PHPCR-36, expand=changesets[-21:-1].revisions[0:29],reviews}, methodType=GET}] : Received status code 503 (Service Temporarily Unavailable)