Can persistent and non-persistent classes be mixed in the hierarchy?
Submissions may assume that if the top-most class is marked as persistent then all its subclasses are marked as non-persistent. Similarly, if a class is marked as non-persistent, then all its subclasses are marked as non-persistent recursively. The motivation for this is that each class that’s marked as being persistent should be transformed to a separate database table. Since sub-classes don’t get transformed to separate tables, marking them as persistent would be slightly misleading.