Task #1883: Store objects as node hierarchy reflecting the object tree?! - TYPO3.TYPO3CR - TYPO3 Forge

Base Distribution TYPO3.Form TYPO3.Imagine TYPO3.Media TYPO3.Neos TYPO3.Neos.NodeTypes TYPO3.Party TYPO3.Setup TYPO3.SiteKickstarter TYPO3.Twitter.Bootstrap TYPO3.TYPO3CR TYPO3.TypoScript Coordination Group Website and Communication

Task #1883

Store objects as node hierarchy reflecting the object tree?!

Added by Karsten Dambekalns almost 7 years ago. Updated about 4 years ago.

Status:

Resolved

Start date:

2008-10-27

Priority:

Must have

Due date:

Assigned To:

Karsten Dambekalns

% Done:

100%

Category:

FLOW3 Persistence

Target version:

Sprint:

Description

Check how this is possible, and how this affects efficiency

Nodetree-from-objects.png - Nodes nested like the objects the represent (and arrays in the mix) (35 kB) Karsten Dambekalns, 2008-11-26 17:37

Associated revisions

Revision 61aa7621
Added by Karsten Dambekalns over 6 years ago

FLOW3, TYPO3CR:

Persistence: rewrote the way object trees are stored in the CR, fixes #1883, fixes #1882

TYPO3CR:

Persistence: array keys are now preserved when persisting, fixes #1620
Persistence: fixed error when persisting DateTime properties, fixes #2195
changed the way properties are added to the Lucene index, fixes #1623, refs #1886
fixed storage backend to enable use of namespaced nodetype names

Lucene, TYPO3CR:

moved the KeywordAnalyser here from TYPO3CR

History

#1 Updated by Karsten Dambekalns almost 7 years ago

Priority changed from Should have to Must have
Target version set to 1.0 alpha 1

#2 Updated by Karsten Dambekalns over 6 years ago

Status changed from New to Accepted
Assigned To set to Karsten Dambekalns

During the recent work on #1882 it turned out that storing objects being part of an aggregate below the root node for that aggregate probably is the easiest and safest way to keep the CR clean when objects are removed from (persistence) repositories.