- The SQL standard specifies a FOR UPDATE clause to be applicable for cursors. Most databases interpret this as being applicable for all SELECT statements. An exception to this rule are the CUBRID and SQL Server databases, that do not allow for any FOR UPDATE clause in a regular SQL SELECT statement. jOOQ simulates the FOR UPDATE behaviour, by locking record by record with JDBC. JDBC allows for specifying the flags TYPE_SCROLL_SENSITIVE, CONCUR_UPDATABLE for any statement, and then using ResultSet.updateXXX() methods to produce a cell-lock / row-lock. Here’s a simplified example in JDBC: + The SQL standard specifies a FOR UPDATE clause to be applicable for cursors. Most databases interpret this as being applicable for all SELECT statements. An exception to this rule are the CUBRID and SQL Server databases, that do not allow for any FOR UPDATE clause in a regular SQL SELECT statement. jOOQ simulates the FOR UPDATE behaviour, by locking record by record with JDBC. JDBC allows for specifying the flags TYPE_SCROLL_SENSITIVE, CONCUR_UPDATABLE for any statement, and then using ResultSet.updateXXX() methods to produce a cell-lock / row-lock. Here's a simplified example in JDBC:
+ Most databases support sequences of some sort, to provide you with unique values to be used for primary keys and other enumerations. If you're using jOOQ's
+ Instead of actually phrasing a select statement, you can also use the
+ You can inline sequence references in jOOQ SQL statements. The following are examples of how to do that: +
+ +
+ For more info about inlining sequence references in SQL statements, please refer to the manual's section about
+ Many RDBMS support the concept of "routines", usually calling them procedures and/or functions. These concepts have been around in programming languages for a while, also outside of databases. Famous languages distinguishing procedures from functions are: +
++ The general distinction between (stored) procedures and (stored) functions can be summarised like this: +
+ ++ In general, it can be said that the field of routines (procedures / functions) is far from being standardised in modern RDBMS even if the SQL:2008 standard specifies things quite well. Every database has its ways and JDBC only provides little abstraction over the great variety of procedures / functions implementations, especially when advanced data types such as cursors / UDT's / arrays are involved. +
+
+ To simplify things a little bit, jOOQ handles both procedures and functions the same way, using a more general
+ If you're using jOOQ's
+ The generated artefacts can then be used as follows: +
+ ++ But you can also call the procedure using a generated convenience method in a global Routines class: +
+ +
+ For more details about
+ Unlike procedures, functions can be inlined in SQL statements to generate
+ The generated artefacts can then be used as follows: +
+ +
+ For more info about inlining stored function references in SQL statements, please refer to the manual's section about
+ Oracle uses the concept of a PACKAGE to group several procedures/functions into a sort of namespace. The SQL 92 standard talks about "modules", to represent this concept, even if this is rarely implemented as such. This is reflected in jOOQ by the use of Java sub-packages in the
+ Apart from this, the generated source code looks exactly like the one for standalone procedures/functions. +
+
+ For more details about
+ Oracle UDTs can have object-oriented structures including member functions and procedures. With Oracle, you can do things like this: +
+ ++ These member functions and procedures can simply be mapped to Java methods: +
+ +
+ For more details about