> So, you think that an API union of strict APIs > is useful? Or did you mean an API intersection > (removing features that aren't available in *both* > databases)?
My wishlist item for this would be: The intersection of exactly those dialects I care about, plus anything that can be emulated without resorting to potentially surprising behaviour. I'm not sure how to organize this, much less implement it; it's definitely an architectural challenge to cleanly cater for all 2^N subsets of N supported dialects, brute-force solutions won't work for that. Maybe it's enough to offer diagnostics. Say, whenever Jooq is configured for dialect, it accepts the dialect to use, and the set of dialects to restrict its API to. That way, Jooq can emit diagnostics if the application tries things that happen to work with the currently selected dialect but wouldn't for other dialects that the application is supposed to be compatible with. Just playing with ideas here... -- 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.
