I have associations at various levels of the hierarchy. Some of which are
"many." I'm trying to avoid having one huge join for all the possible
sub-classes. Yes, a bunch of smaller queries would be preferred. (Assuming
they don't repeat/overlap each other a lot.)
On 1/30/08, Christopher Lamey <[EMAIL PROTECTED]> wrote:
>
> So are you basically looking at one big query with a bunch of joined
> tables
> or a bunch of smaller queries to pull it all together?
>
> If so, which one would fit better for your app?
>
> On 1/29/08 6:42 PM, "Hugh Ross" <[EMAIL PROTECTED]> wrote:
>
> > I have the good fortune to work on a large domain model, part of which
> uses
> > too much inheritance. I don't want to use a huge outer join with 15 or
> 20
> > tables in it. I'm wondering if I can use RowHandlers to help. In
> > particular, is it possible for a RowHandler to replace the object passed
> to
> > the handleRow method?
> >
> > E.g.,
> > **
> > *public void handleRow (Object valueObject)
> > throws SQLException {
> > Person person = (Person) valueObject;
> > valueObject = MyFactory.createSubClassObject( person );*
> > *}
> > *
> > Any other sample solutions to this kind of problem are also most
> welcome...
> > *
> > *
>
>
