Re: [Hibernate-devel] Multitable Persitency

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

>I started to mess around with the source. I allready made the Schema
>Genarator work with my first test.

cool. which means you came into contact with the cirrus.hibernate.map
package, presumably? That code is an abomination (partly because it
currently tolerates all versions of the mapping dtd back to 0.9.1).

>- how about this version column? its just something that can be declared
>in one of the superclasses and should be inherited to the subclass - am
>i correct?

Yes, exactly. Theres going to be some subtleties related to this .....
lets worry about them later, though.

>Doing Inserts:
>I will have to do multiple Inserts. So if a polymorphic Class has it own
>table i will first call the parent classes insert Statement and then
>the classes own statement.

yeah cool. Is the best way to have two ClassPersister subclasses or to
have a whole bunch of ugly if/elses in ClassPersister? Presently
ClassPersister is a final class with very many final fields....

>The only question that arises is native key
>generation. I will try not to use native generation uneless this is the
>root table of the polymorphic chain and then use this key in the other
>inserts that follow.

Cool. Hadn't occurred to me.

> The source look quite nice and is mostly very readable. I hope I can
> keep the Standard.

Please flag confusing areas to me, so we can improve them. (And if
you spend a few minutes looking at something and then figure it out,
please add a comment.) Everything was built very XP-style from the
start, ie. there was no upfront design or formal requirments, only
the automated tests.

peace