Hello,
It was crucial for us to use lazy fetching on a main entity in our application to avoid having a tile been downloaded in 30 secondes for just 50 instances of this entity. With Hibernate 2, it was ok for all the association except for many-to-one associations (no attribute lazy can be put on it in Hibernate2). We update to Hibernate 3.0.5, to take advantage of the last changes in androMDA hibernate cartridge to generate the new lazy attributes on many-to-one. The mapping file was generated as we want. But, except having a little improvement on the time to download due to the new default policy of hibernate 3 to fetch the dependent tables in (by selects rather than joins), nothing were changed. It seems to be the normal behavior for the hibernate 3.0.5 since a new value on the lazy attribute (lazy="proxy") were introduce to use class proxies. Lazy attributes on class or lazy with "proxy" value being still impossible on andromda hibernate cartridge, we decided so to use a previous version: hibernate 3.0.1 (the pb was the same with 3.0.3), and all seems to work as we expected (for the moment...). Lazy attribut was taken into account. Hope this will help someone. -- nash360 _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=3259#3259 Posting to http://forum.andromda.org/ is preferred over posting to the mailing list! ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Andromda-user mailing list Andromda-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/andromda-user
