Geert Bevin <gbevin <at> uwyn.com> writes: > > Hi John, > > no hierarchies are not supported. This is one of the things lacking. > You'll have to do some custom coding. Of course you will not be able > to create the table structure from the install method, but you should > be able to restore, save and delete your beans to the single table. > Excess columns should simply be ignored. For ease of use, I'd create > DAO that handled the type column and has appropriate methods to > handle each type. If you design these methods properly, you shouldn't > even need to cast. > > I know that this isn't much help, but I hope it still provided you > with some useful info. > > Best regards, > > Geert
So, actually, there is some support for inheritance. If B extends A, the fields from A are included in the database. This is pretty much a table-per- concrete-class approach, a valid approach for many situations. There are some drawbacks, but it is workable. Just in case I haven't given enough annoying ideas lately... I would think it would be pretty straightforward to provide for a one-table-per-class (concrete and abstract) approach. Maybe I'll poke around at that some day. Anyway, thanks for the help and the cool db layer. - JT _______________________________________________ Rife-users mailing list [email protected] http://lists.uwyn.com/mailman/listinfo/rife-users
