RE: [Hibernate-devel] Multi Table Support

[Gavin_King/Cirrus%<CI...@ci...>]

>What about the option of defining a custom map object for a class.  For
>those special cases  (such as multiple table mappings), the custom map
>could handle the mapping to the database using hand coded SQL.

I've wondered about that in the past, but I can't imagine how we could
possibly integrate such objects with the query language.

I don't want to implement something like this at this stage just because
of the cost to the complexity of the already-too-complex core persistence
engine (ie. RelationalDatabaseSession.java). Right now this doesn't pass
my bloat-filter.

Now, a challenge to everyone here:

  How can we componentize RelationalDatabaseSession?

I would *love* to refactor this class into a few different classes but I
can't see how to do this without making the code actually *less* rather
than *more* readable. If there are any hardcore OO modellers here, lets
see what you can come up with!

There is one refactoring planned already (for 1.0.3) - namely factoring
all the find/iterate/etc code out to a seperate class the implements
a new paginating cirrus.hibernate.Query interface. This will actually
do a lot to help the situation, i think. But other suggestions are *very*
welcome!