[TYPO3-mvc] Tx_Extbase_MVC_Controller_Argument StoragePage

[Karsten Dambekalns]

Hi.

On Tue, 22 Jun 2010 08:30:06 +0200, Sebastian Kurfürst  
<sebastian at typo3.org> wrote:
> 1) Using the repository findByUid method, as suggested.

Nice idea, but we should think this through thoroughly. Currently all data  
is fetched and then mapped (more or less), this new approach would lead to  
more scattered reads. And we don't need that solution in FLOW3, as we  
don't have the problem, see below. Anyway, feel free to open a feature  
ticket on Forge for this, so it is not forgotten and can be discussed  
further.

> 2) Overriding the query settings with

Well, settings like those are not part of FLOW3, so feel free to do what  
you like :)

Generally, using a storage pid seems like a bad idea, as it leads to such  
problems. Anyway, I remember suggesting the use of the GRSP for Extbase -  
it could be used in addition to a specific storage page for "shared  
objects". Similarly records on pid 0 could included automatically.

But, again: IMHO an object tree is an object tree and objects should be  
retrieveable by their identity/identifier in any case, regardless of the  
storage page.

Regards,
Karsten