[TYPO3-mvc] Respect storage page ignored on object properties
Thomas "Thasmo" Deinhamer
thasmo at gmail.com
Wed May 19 00:47:13 CEST 2010
Does somebody have a hint for me?
Thanks a lot,
Thomas
Am 14.05.2010 12:11, schrieb Thomas "Thasmo" Deinhamer:
> Hello Felix and thanks for your reply!
>
> Your seuggestion to comment out the line should have the same result as
> my try to set it to TRUE.
>
> (Quote: "It seems that setting the respect storage page to TRUE on line
> 357 in the DataMapper.php has no effect.")
>
> I think you're refering to the same line as me.
>
> So, this doesn't help - but I'm not sure where the join is done.
>
> Any other ideas?
>
> Thanks a lot,
> Thomas
>
> Am 14.05.2010 11:16, schrieb Felix Oertel:
>> Hi,
>>
>> Am 14.05.10 02:27, schrieb Thomas "Thasmo" Deinhamer:
>>> I'm not sure but in my case this occurs with objects having a m:n
>>> relation further a 'RELATION_HAS_AND_BELONGS_TO_MANY' relation.
>>
>> this applies to n:m relations as well as 1:n relations.
>>
>>> It seems that setting the respect storage page to TRUE on line 357 in
>>> the DataMapper.php has no effect.
>>
>> for 1:n and n:m relations this is overwritten in
>> DataMapper:getPreparedQuery()
>>
>> $query->getQuerySettings()->setRespectStoragePage(FALSE);
>>
>> to get database rows out of an _not_ 1:1 relation, extbase has to join
>> about at least two tables. i could imagine extbase has problems to
>> decide which database the .pid-condition applies to, but that's just a
>> quick guess. if you want to digg deeper into that, just comment that
>> line and look what happens to your querry ;)
>>
>>> I'm not into OOP too much so it seems I'm running in circles all the
>>> time.
>>
>> I would not go mad about that. ;-) The database layer in extbase is as
>> powerful as complicated. there is not this "one place" where alle the
>> stuff happens but it's spread over several classes. you will get into
>> that with time goin' by ... ;-)
>>
>> regards, foertel
More information about the TYPO3-project-typo3v4mvc
mailing list