configuration / preloading
1 view
Skip to first unread message
mindplay.dk
Aug 14, 2010, 10:47:56 AM8/14/10
to Outlet ORM
Looking at the Outlet constructor, it appears that all the maps and
associations are created in advance?
While that's probably fine for small applications with 10-20 entities,
that's not a very scalable approach - if you have an application with
100-200 entities, creating all of these objects on every request is
going to add significant overhead.
Wouldn't it be a better strategy to have getEntityMap() construct the
requested mappings on-demand?
associations are created in advance?
While that's probably fine for small applications with 10-20 entities,
that's not a very scalable approach - if you have an application with
100-200 entities, creating all of these objects on every request is
going to add significant overhead.
Wouldn't it be a better strategy to have getEntityMap() construct the
requested mappings on-demand?
mindplay.dk
Aug 14, 2010, 10:48:22 AM8/14/10
to Outlet ORM
> Wouldn't it be a better strategy to have getEntityMap() construct the
> requested mappings on-demand?
Luís Otávio
Aug 14, 2010, 12:15:47 PM8/14/10
to outle...@googlegroups.com
Thats is awesome
--
You received this message because you are subscribed to the Google Groups "Outlet ORM" group.
To post to this group, send email to outle...@googlegroups.com.
To unsubscribe from this group, send email to outlet-orm+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/outlet-orm?hl=en.
Reply all
Reply to author
Forward
0 new messages