table has all of
these columns. The backing classes are distinct, though: in general, you'd work
with Users, but if you need a FooUser, you ask the relevant User for its
FooUser. The win is that you're not re-inventing User for every new app. It
resembles single table inheritance,
tity.
Let me ask a more general question then. How do Cayenne users achieve code
reuse (or even entity/model reuse)? Presumably people aren't re-writing their
"User" entity, for example, from scratch for every application. Is there any
comparable approach for "reuse but customise