[TYPO3-mvc] Domain model records without pid-column

Sebastian Kurfürst sebastian at typo3.org
Mon May 24 11:30:50 CEST 2010


Hey,

> And just fyi, at present Extbase does care about the storage page when
> retrieving objects via repository, but it does NOT care about storage
> page when retrieving objects via object property like
> $blog->getAllPosts(); this will fetch all posts, regardless on which
> page they are stored, either on the same domain or on any other in the
> TYPO3 installation.
Exactly, that's correct behavior as well. For the following reason:

- if, in TYPO3 backend, you relate records together, you can "jump" from
one page to another as well, if you want to.
- Imagine we would only fetch the related records from the current
storage page: Then, not all relations which are set in the TYPO3 backend
will be seen in Extbase, only those on one page.
- Imagine, one adds a record from a different page to an aggregate; and
the object storage only contains records from the storage page: Then,
the record would have to be moved, else, it could not be found again.

So, in summary, I think it's all correct behavior, it just has to be
explained more thoroughly :-)

> Imho it's good to have a storage page set all time. But at present it's
> a bit unclear and confusing how it all works. Maybe there should be
> seperate page ids for reading and storing objects, or they should even
> be setable/unsetable via API before querying objects.
See above :)


Greets,
Sebastian


More information about the TYPO3-project-typo3v4mvc mailing list