If the classes in your system vary a lot in behavior but not in their internal state then mapping to a database can be straightforward.
With lots of variations in object structure things can be horrible - witness designs that have more tables than most tables have rows.
> With lots of variations in object structure things can be horrible - witness designs that have more tables than most tables have rows.
This is the problem document databases are designed to solve. :)
OO really shines with UI programming, where incrementally building up behaviour through inheritance makes a lot of sense.