> More seriously, since Jooq's mission is "database first", JDBC conventions > are probably not an authoritative source for DB encoding conventions.
I trust that the JDBC specification was made by an expert group based on well-informed "database-first" decisions. In particular, this case is not a convention but behaviour by specification. JDBC drivers are to adhere to this specification. Hence the abstraction provided by JDBC over any underlying database is trustworthy enough for jOOQ to rely on - unless there is some specification ambiguity that I have now overlooked...? -- 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.
