Feature #6006
Base FLOW3 persistence directly on database, not on TYPO3CR
Status:
Resolved
Priority:
Must have
Assignee:
Category:
Persistence
Target version:
Start date:
2010-01-13
Due date:
% Done:
100%
Estimated time:
PHP Version:
Has patch:
Complexity:
Description
Once upon a time we decided to use JSR-283 for storing our content. That still makes sense for the CMS, but for the framework it turned out to be too much overhead and being in the way of elegantly using TYPO3CR for the CMS (because it always feels like using something that we shouldn't use because it's infrastructure...).
So, create a FLOW3 persistence backend that directly uses a DB.
Updated by Karsten Dambekalns over 12 years ago
- Status changed from Accepted to Resolved
- % Done changed from 90 to 100
Applied in changeset r3616.