Ok I understand far better. The modeler could support this by allowing a
different DataObject superclass for each ObjEntity. AFAIK it would be
painless since getting and setting properties is just a matter of
"readProperty" or "writeProperty".
Thanks a lot, Cayenne is real good work, far more understandable and
less dependant of JBoss than Hibernate... (not to mention other
problems, but I'm not here to flamme anyone)
Mikael.
Andrus Adamchik wrote:
>Let me clarify the likely source of confusion. PostgreSQL supports
>inheritance at the DB level:
>http://www3.ca.postgresql.org/docs/current/static/tutorial-inheritance.html
>This is one of the cool features of PostgreSQL (and I only learned about
>it today myself). But to the best of my knowledge it is not a part of SQL
>standard, and I am not aware of other DB engines supporting that. Also
>JDBC doesn't support any metadata about Postgres table inheritance (unless
>there are some Postgres driver-specific extensions?), and thus
>reverese-engineering procedure treats those tables as independent from
>each other.
>
>So from Cayenne perspective this type of mapping won't be "single table"
>anymore, and you should probably keep the default created Java mapping.
>
>
This archive was generated by hypermail 2.0.0 : Wed Oct 13 2004 - 15:09:55 EDT