Calling stored functions/procedures from jOOQ
Once you start dealing with stored functions/procedures across different database vendors, you'll be hit by the lack of standardization. For instance, the vendor-specific syntax for expressing functions/procedures, the wide variety of vendor-specific functions/procedure types, and different ways of supporting and treating the output parameters are just a few non-standard aspects of stored functions/procedures.
Calling stored functions/procedures via plain JDBC code is not easy either, especially if advanced data types are involved (for instance, arrays or UDTs). But, as you already know, using the jOOQ DSL saves us from interacting directly with the JDBC API, so it saves us from making cutting-edge decisions regarding JDBC workarounds.
The jOOQ DSL represents stored functions/procedures via the org.jooq.Routine API, so there is a common API for both. Whenever the jOOQ generator detects a stored function/procedure it generates...
