Feature #32148
closed
Task #33745: Integrate File Abstraction Layer
Integrate TCA Relation Service
Added by Steffen Ritter almost 13 years ago.
Updated over 12 years ago.
Description
Currently you need to resolve relations between TCA-tables yourself our use t3lib_loadDBGroup.
The interface for usage of load-db-group is not object-oriented designed, very hard to use, needs external preparation and knowledge about internals for usage.
To ease this up for developers add an "relation-service" for doing this in a more "object-orientated" way, with a single point of action.
In the first step this acts only as a wrapper for t3lib_loadDBgroup but in long term loaddbgroup should be migrated and reworked in a clean way into the the relation-service.
- Status changed from Accepted to Under Review
Patch set 1 of change I8d0cd3fa302683e952f600041dad66e8a4a237bc has been pushed to the review server.
It is available at http://review.typo3.org/6969
Patch set 2 of change I8d0cd3fa302683e952f600041dad66e8a4a237bc has been pushed to the review server.
It is available at http://review.typo3.org/6969
Patch set 3 of change I8d0cd3fa302683e952f600041dad66e8a4a237bc has been pushed to the review server.
It is available at http://review.typo3.org/6969
- Target version changed from 4.7.0-alpha1 to 4.7.0-alpha2
- Target version changed from 4.7.0-alpha2 to 4.7.0-alpha3
- Subject changed from Add objective wrapper for ancient t3lib_loaddbgroup to Integrate TCA Relation Service
- Parent task set to #33745
The current implementation of the relation service is bound to table:field and optionally a table or field or any relation to be looked up. I think this is very complex for the basic scope of the service object. Thus, I'd like to suggest the following:
$service = new t3lib_tca_RelationService($table, $field);
$relation = $service->to($relatedTable, $relatedField);
$relatedRecods = $relation->getRecordsFor($record);
$relatedUids = $relation->getUidsFor($record);
So we have:
- t3lib_tca_RelationService
- t3lib_tca_Relation
- Status changed from Under Review to On Hold
In favor of a simple functionality, this is on hold and not a requirement for the file abstraction layer...
- Target version changed from 4.7.0-alpha3 to 4.7.0-beta1
- Target version deleted (
4.7.0-beta1)
- Status changed from On Hold to Rejected
Also available in: Atom
PDF