[FLOW3-general] Problem with Object-Associations after having updated to FLOW3 1.1rc2

[Regine Rosewich]

Hi Karsten,

I dug myself a bit into the documentation of doctrine-2 and did a lot of tests. I finally found out that it had to do with the ManyToMany Associations I used(don't ask me what exactly caused the problems, but the Doctrine-Hydration produced ten-thousands of Queries when inserting one object). So I decided to give up any ManyToMany Association by splitting them into two OneToMany Associations with a dedicated Join-Class between. Additionally I use 'fetch="EXTRA_LAZY"' whenever it makes sense.

My application now is flashingly fast again (whooow!) and the use of the join-classes makes the architecture of the application much more handy as I feel.

I for myself would recommend not to use ManyToMany Associations if a lot of data are 'in the game'.

Regine

aurum Gesellschaft für Unternehmens-
beratung und Integration m.b.H

Höllenberg 12
79348 Freiamt
DEUTSCHLAND

Sitz: Freiamt - Handelsregister Freiburg HRB 260865
Geschäftsführerin: Regine Rosewich

Diese E-Mail enthält vertrauliche und/oder
rechtlich geschützte Informationen. Wenn 
Sie nicht der richtige Adressat sind oder
diese E-Mail irrtümlich erhalten haben,
informieren Sie bitte den Absender
und vernichten Sie diese E-Mail.
Das unerlaubte Kopieren sowie die unbefugte
Weitergabe dieser E-Mail ist nicht gestattet.

This e-mail may contain confidential and/or
privileged information. If you are not the intended recipient (or have received this 
e-mail in error) please notify the sender immediately and destry this e-mail. 
Any unauthorized copying, disclosure or
distribution on the material in this e-mail
is strictly forbidden.

Am 29.08.2012 um 11:12 schrieb Karsten Dambekalns:

> Hi.
> 
> On 20.08.12 12:06, Regine Rosewich wrote:
>> With FLOW3 1.0 updating and adding items to the main object/class worked
>> fine and satisfyingly performant. With FLOW 1.1rc adding one item produces
>> 20!! MB of Query-Log (with tons of queries to the associated tables) and
>> takes 5!! Minutes compared to some seconds with FLOW3 1.0. 
> 
> I am puzzled, to be honest. I have no idea what could cause this…
> 
> Would it be possible to get at the code, to try and reproduce this locally?
> 
> Did you change your models with the upgrade?
> 
> Can I see the output of
> ./flow3 doctrine:entitystatus --dump-mapping-data
> for both versions? (Note, apply the patch at
> https://gist.github.com/3508881 to 1.0 first, or that won't work!)
> 
> Regards,
> Karsten
> -- 
> Karsten Dambekalns
> TYPO3 Core Developer, FLOW3 / Phoenix Team
> 
> TYPO3 .... inspiring people to share!
> Get involved: typo3.org
> _______________________________________________
> FLOW3-general mailing list
> FLOW3-general at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/flow3-general