> Another interesting point is this one: > > "A table can inherit from more than one parent table, in which > case it has the union of the columns defined by the parent tables." > > This simple statement will prevent any type of inheritance-mapping > between SQL and Java, as Java does not support multiple inheritance. > In this case, I'm pretty glad it doesn't, as the power of multiple > inheritance is only exceeded by its mystery, as my coworkers say ;-)
Good point. But maybe jOOQ could still support inheritance-mapping when only single-inheritance is used in the database. Wouldn't it be possible to work around this by letting the 'user facing' types (Cities, CitiesRecord, etc.) be interfaces instead of classes?
