Hello,
we have varchar2 columns which should not be null, but are allowed to
contain an empty string. So from our perspective, the oracle implementation
of empty string -> store as null does not hurt per se; however, the
handling on the jooq side is a bit cumbersome (not because of jooq, but
because of oracle):
set(field, "") // ok-ish (can't get any better with oracle)
get(field, "") // returns null
where(field.eq("")) // not true
where(field.isNull()) // this is in fact field.eq("")
So, is there a best practice or jooq option to handle such use cases
without having to be extra careful on every usage of the field to handle
the special case properly?
(Bonus question: is there a way to handle the general varchar case
cross-database-safe?)
Thank you
Nico
--
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.
