Base FLOW3 persistence directly on database, not on TYPO3CR
|Priority:||Must have||Due date:|
|Assignee:||Karsten Dambekalns||% Done:||
|Target version:||TYPO3 Flow Base Distribution - 1.0 alpha 7|
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.
[+FEATURE] FLOW3 (Persistence): Wrote a new persistence backend using a database directly instead of TYPO3CR. Details see below. Resolves #6006.
[+API] FLOW3 (Persistence): Added new backend classes that can be used for further backends.
[-API] FLOW3 (Persistence): Removed methods getIdentifierByObject(), getObjectByIdentifier() and isNewObject() from BackendInterface.
[+API] FLOW3 (Persistence): Removed methods getIdentifierByObject(), getObjectByIdentifier() and isNewObject() to ManagerInterface and Manager.
[-API] FLOW3 (Persistence): Removed withUUID() from QueryInterface, use getObjectByIdentifier() on Manager instead.
[+API] FLOW3 (Persistence): Added constants for query operators to QueryInterface.