Refactor MetaMapper to make it more extensible? :)
2010/2/15 Jeppe Nejsum Madsen
> Hi,
>
> Using PreCache in mapper seems crucial to avoid N+1 select issues and
> works fine for simple FK relationships. I have a model where I need
> something more advanced and would like to avoid doing manual queries:
>
> 1) More than 1 FK level eg. obj1 -> fk1 -> fk2
> 2) Loading a collection ala OneToMany. ie I select 500 records that
> each have 1-10 members in a collection.
>
> Has anybody tried stuff like this? Looking at the code in MetaMapper
> it doesn't exactly look like this area is very extensible. Any hints
> how to proceed? Or is this futile?
>
> /Jeppe
>
> --
> You received this message because you are subscribed to the Google Groups
> "Lift" group.
> To post to this group, send email to lift...@googlegroups.com.
> To unsubscribe from this group, send email to
> liftweb+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/liftweb?hl=en.
>
>
--
You received this message because you are subscribed to the Google Groups
"Lift" group.
To post to this group, send email to lift...@googlegroups.com.
To unsubscribe from this group, send email to
liftweb+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en.
