Actually now that I have thought about the idea a little more, I am less keen on it. My problem with it will be performance. E.g. the pop LIST command currently (using the hibernate implemenation that I will commit tonight) can return all of the necessary information with a single query, with no joins, filtered only by a single foreign key (very quick). The schema needed to support JSR-170 will mean that more than a single row for each entry in the LIST result set, meaning joins and probably a fair bit of trickery to avoid the n+1 queries thing. We can get better performance & scalability with a schema explictly modeled for our objects and still have a clean design.
Mike.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3882451#3882451
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3882451
|
