I played with the Cayenne Java ORM last week. I didn't like it much
(it's very inferior to RDBO, especially in auto-generating from the
schema), but one idea that caught my eye was the 'auto' hierarchy.
Basically you get a hierarchy like this (naming simplified):
cayenne.BaseObject
parent of
db.auto.A
parent of
db.A
where auto.A inherits from BaseObject, and A inherits from auto.A.
Customizations go in A. All the glue code (what
Rose::DB::Object::Loader woult generate) goes in db.auto.A. Only the
db.auto.* classes are regenerated after the first run (unless you
explicitly ask to overwrite the db.* classes). You can set the base
object to something other that BaseObject.
Rose::DB::Object::Loader already supports base objects, but not this
kind of hierarchy AFAIK. I like the idea of the auto hierarchy, since
it allows me to regenerate from a changed DB schema without killing any
customizations in the DB classes. I don't think it's a hard thing to
do as far as the Loader, either.
Ted
-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Rose-db-object mailing list
Rose-db-object@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rose-db-object
