Task #1481
Implement referential integrity for reference properties
| Status: | Resolved | Start date: | 2008-09-09 | |
|---|---|---|---|---|
| Priority: | Must have | Due date: | ||
| Assigned To: | Karsten Dambekalns | % Done: | 100% |
|
| Category: | Property handling | |||
| Target version: | - | |||
| Sprint: |
Description
Removing a node should not be possible when there are still references to that node.
Creating a reference property to a non-existant node should not be possible.
How would this interact with the persistence layer above the repository layer?
Might lead to problems if it tries to do operations in the wrong order.
Associated revisions
TYPO3CR:
- Property objects returned by get[Weak]References() now have the correct parent node
- removal of a node is no longer possible if the node has "external" references pointing to it, fixes #1481, refs #1482
- some optimisations to get rid of misused exceptions and to speed up things in getDepth(), getPath(), getRootNode()
- the JSON controller is now a service properly based on RESTController
- some cleanup to NodeTest and SessionTest
History
#1 Updated by Karsten Dambekalns almost 7 years ago
- Priority changed from Should have to Must have
- Target version set to 197
#2 Updated by Karsten Dambekalns over 6 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
Applied in changeset r1524.
#3 Updated by Karsten Dambekalns over 6 years ago
- Category set to Property handling
- Assigned To set to Karsten Dambekalns
#4 Updated by Robert Lemke about 4 years ago
- Target version deleted (
197)