I didn't see an option for this, but I was wondering if it was possible to
give preference for primitive data types in the interface that are being
generated.
ie. boolean over Boolean, long rather then Long etc.
I like the idea of interface to help ensure the Listing objects we create
is consistent with the data model but we try to avoid nulls since they
introduce those tristate use cases that are undefined.
ie. Boolean = { yes, no... uhmm.. maybe? } a lot of times null introduces
an undefined state that is usually preferred to be avoid to represented as
an enum rather then boolean.
Is there an option to allow such behavior?
--
Thank you
Samir Faci
https://keybase.io/csgeek
--
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.
