[TYPO3-mvc] Respect storage page ignored on object properties

Martin Kutschker masi-no at spam-typo3.org
Mon May 31 15:44:34 CEST 2010


Jochen Rau schrieb:
> Hi Masi.
> 
> On 31.05.10 15:19, Martin Kutschker wrote:
>>> You might argue, that Repositories *are* restricted to search only on
>>> the storagePids. So why doesn't this apply to related objects (like
>>> products), too? The objects/aggregates you fetch from a repository via
>>> its find*() methods are a selection of the "whole world" (in most
>>> cases). That's what repositories are made for.
>>
>> This approach leads to problems when the installation hosts many
>> domains or organizational units
>> that don't share data. So IMHO it must be possible to partition the
>> repository by PID. Of course
>> it's true that has nothing to do with the domain itself. Is has only
>> to do with the resources the
>> repository uses (ie the storage PID has the same significance as the
>> database connection data).
> 
> That's what I (tried) to describe ;-). Repositories are constrained by
> PID, Associations of aggregates must not.

Okay. Any group of repositories may have only relations within the same "partition".

eg If you have two domains which share product categories the category relations may be fetched from
the world. OTOH if the categories are also separated than you shouldn't even be allowed to add a
category that's not inside your "partition" (ie within the same storage PID).

In this scenario it is for me an error if the repository returns relations outside of the
"partition". Even if this can only happen if you fiddle with the DB manually (ie are not using the
repository API).

Masi


More information about the TYPO3-project-typo3v4mvc mailing list