That went off too early...
2014-12-18 18:47 GMT+01:00 Lukas Eder <[email protected]>:
>
> Hello
>
> 2014-12-16 16:54 GMT+01:00 <[email protected]>:
>>
>> What do you want to do?
>>>
>>
>> Basically:
>> - use PG inheritance
>> - use Java inheritance
>> - use JOOQ
>> - have clean code
>>
>> If I understand correctly the first part of your answer, I'll be able to
>> generate POJOs for:
>> - Parent
>> - ChildA
>> - ChildB
>>
>
> Yes, with all columns in Parent being repeated in ChildA and ChildB
>
>
>> But I won't have the inheritance link out of the box.
>>
>
>
Exactly, although you could work around this limitation by injecting
interfaces:
<pojoImplements>com.example.MyOptionalCustomInterface</pojoImplements>
http://www.jooq.org/doc/3.5/manual/code-generation/codegen-matcherstrategy/
>
>> Since Java does not allow me to write
>> class enhancedClassA extends Parent, ChildA
>> I can't find a clean way to get all PG / Java / JOOQ features working
>> together.
>>
>> I hope you'll get what I mean.
>>
>
Yes, well we already have all inheritance information in jOOQ-meta via
TableDefinition.getChildTables() and getParentTable(). You might be able to
extend the JavaGenerator to generate your own POJOs the way you like them
to be. It's just that we haven't gotten around to providing a generally
acceptable solution yet, but we most definitely want to support ORDBMS
inheritance in the future.
Let me know if that would be a viable solution for you.
Best Regards,
Lukas
--
You received this message because you are subscribed to the Google Groups "jOOQ
User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
