Dealing with differences between Object Model and Data Model

Generally our CSLA business objects correspond 1-to-1 with our database tables. 

MamaWidget is persisted to mamawidget_table

and

BabyWidget is persisted to babywidget_table

Problem is MamaWidget is so fat....I said MamaWidget is SO FAT...How fat is she?

MamaWidget is SO FAT her property list looks like the list of ingredients in a twinkie.

Alright, excuse the poor attempt at humor.  Point is the parent object has gotten too bloated and I would like to decompose some of it into a few child objects, but this should not effect the persistance, which saves all editable property values to a single table.

This deviates from the way we tend to wire up our CSLA objects, but seems like the right thing to do.  I don't want to change the database schema, just the object hierarchy. 

Is there an example of persisting a business object with children into a flattened schema?

Thanks.