> This feature request is really very simple.
> Inheritance is used only for the purpose of
> being able to "tweak" generated classes to
> hold new, custom methods.

The issue isn't the intended purpose, but the potential side effects.

What's worrying me most is the use case where people want to organize some of 
their entity classes as superclass and subclass.
I.e. the application programmer wants

  class BarRecord extends FooRecord

and can't make BarRecord a subclass of BaseBarRecord anymore.
I don't see any way around this, other than telling people that inheritance 
between entity classes is incompatible with double-class generation.

-- 
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/groups/opt_out.

Reply via email to