diff --git a/jOOQ/src/main/java/org/jooq/impl/DSL.java b/jOOQ/src/main/java/org/jooq/impl/DSL.java index 62975c8192..4374161650 100644 --- a/jOOQ/src/main/java/org/jooq/impl/DSL.java +++ b/jOOQ/src/main/java/org/jooq/impl/DSL.java @@ -12622,22 +12622,46 @@ public class DSL { *
* This constructs a field reference given the field's qualified name. jOOQ *
- * Example:
+ * Example:
+ *
+ *
+ *
* // This field...
* field(name("MY_SCHEMA", "MY_TABLE", "MY_FIELD"));
*
* // ... will render this SQL by default, using the SQL Server dialect
* [MY_SCHEMA].[MY_TABLE].[MY_FIELD]
- *
+ *
+ *
* - * Another example:
+ * Another example:
+ *
+ *
+ *
* create.select(field("length({1})", Integer.class, field(name("TITLE"))))
* .from(table(name("T_BOOK")))
* .fetch();
*
* // ... will execute this SQL on SQL Server:
* select length([TITLE]) from [T_BOOK]
- *
+ *
+ *
+ * + * NOTE: A lot of things work less well in jOOQ if no + * {@link DataType} information is attached to a {@link Field} expression, + * including: + *
NULL values.- * A PlainSQLField is a field that can contain user-defined plain SQL, + * A plain SQL field is a field that can contain user-defined plain SQL, * because sometimes it is easier to express things directly in SQL, for * instance complex proprietary functions. There must not be any binding * variables contained in the SQL. *
* Example: *
- *
+ *
+ *
+ *
* String sql = "DECODE(MY_FIELD, 1, 100, 200)";
- *
+ *
+ *
+ * + * NOTE: A lot of things work less well in jOOQ if no + * {@link DataType} information is attached to a {@link Field} expression, + * including: + *
NULL values.* NOTE: When inserting plain SQL into jOOQ objects, you must * guarantee syntax integrity. You may also create the possibility of @@ -14132,16 +14175,35 @@ public class DSL { /** * Create a "plain SQL" field. *
- * A PlainSQLField is a field that can contain user-defined plain SQL, + * A plain SQL field is a field that can contain user-defined plain SQL, * because sometimes it is easier to express things directly in SQL, for * instance complex proprietary functions. There must not be any binding * variables contained in the SQL. *
* Example: *
- *
+ *
+ *
+ *
* String sql = "DECODE(MY_FIELD, 1, 100, 200)";
- *
+ *
+ *
+ * + * NOTE: A lot of things work less well in jOOQ if no + * {@link DataType} information is attached to a {@link Field} expression, + * including: + *
NULL values.* NOTE: When inserting plain SQL into jOOQ objects, you must * guarantee syntax integrity. You may also create the possibility of @@ -14162,16 +14224,35 @@ public class DSL { /** * Create a "plain SQL" field. *
- * A PlainSQLField is a field that can contain user-defined plain SQL, + * A plain SQL field is a field that can contain user-defined plain SQL, * because sometimes it is easier to express things directly in SQL, for * instance complex proprietary functions. There must be as many binding * variables contained in the SQL, as passed in the bindings parameter *
* Example: *
- *
+ *
+ *
+ *
* String sql = "DECODE(MY_FIELD, ?, ?, ?)";
- * Object[] bindings = new Object[] { 1, 100, 200 };
+ * Object[] bindings = new Object[] { 1, 100, 200 };
+ *
+ * + * NOTE: A lot of things work less well in jOOQ if no + * {@link DataType} information is attached to a {@link Field} expression, + * including: + *
NULL values.* NOTE: When inserting plain SQL into jOOQ objects, you must * guarantee syntax integrity. You may also create the possibility of @@ -14194,7 +14275,7 @@ public class DSL { /** * Create a "plain SQL" field. *
- * A PlainSQLField is a field that can contain user-defined plain SQL, + * A plain SQL field is a field that can contain user-defined plain SQL, * because sometimes it is easier to express things directly in SQL, for * instance complex proprietary functions. There must not be any binding * variables contained in the SQL. @@ -14226,7 +14307,7 @@ public class DSL { /** * Create a "plain SQL" field. *
- * A PlainSQLField is a field that can contain user-defined plain SQL, + * A plain SQL field is a field that can contain user-defined plain SQL, * because sometimes it is easier to express things directly in SQL, for * instance complex proprietary functions. There must not be any binding * variables contained in the SQL. @@ -14258,7 +14339,7 @@ public class DSL { /** * Create a "plain SQL" field. *
- * A PlainSQLField is a field that can contain user-defined plain SQL, + * A plain SQL field is a field that can contain user-defined plain SQL, * because sometimes it is easier to express things directly in SQL, for * instance complex proprietary functions. There must be as many binding * variables contained in the SQL, as passed in the bindings parameter @@ -14292,7 +14373,7 @@ public class DSL { /** * Create a "plain SQL" field. *
- * A PlainSQLField is a field that can contain user-defined plain SQL, + * A plain SQL field is a field that can contain user-defined plain SQL, * because sometimes it is easier to express things directly in SQL, for * instance complex proprietary functions. There must not be any binding * variables contained in the SQL. @@ -14323,7 +14404,7 @@ public class DSL { /** * Create a "plain SQL" field. *
- * A PlainSQLField is a field that can contain user-defined plain SQL, + * A plain SQL field is a field that can contain user-defined plain SQL, * because sometimes it is easier to express things directly in SQL, for * instance complex proprietary functions. There must not be any binding * variables contained in the SQL. @@ -14354,7 +14435,7 @@ public class DSL { /** * Create a "plain SQL" field. *
- * A PlainSQLField is a field that can contain user-defined plain SQL,
+ * A plain SQL field is a field that can contain user-defined plain SQL,
* because sometimes it is easier to express things directly in SQL, for
* instance complex proprietary functions. There must be as many binding
* variables contained in the SQL, as passed in the bindings parameter
@@ -14428,16 +14509,40 @@ public class DSL {
* This is useful for constructing more complex SQL syntax elements wherever
* Field types are expected. An example for this is MySQL's
* GROUP_CONCAT aggregate function, which has MySQL-specific
- * keywords that are hard to reflect in jOOQ's DSL:
+ * keywords that are hard to reflect in jOOQ's DSL:
+ *
+ *
+ *
* GROUP_CONCAT([DISTINCT] expr [,expr ...]
* [ORDER BY {unsigned_integer | col_name | expr}
* [ASC | DESC] [,col_name ...]]
* [SEPARATOR str_val])
- *
+ *
+ *
* - * The above MySQL function can be expressed as such:
+ * The above MySQL function can be expressed as such:
+ *
+ *
+ *
* field("GROUP_CONCAT(DISTINCT {0} ORDER BY {1} ASC SEPARATOR '-')", expr1, expr2);
- *
+ *
+ *
+ * + * NOTE: A lot of things work less well in jOOQ if no + * {@link DataType} information is attached to a {@link Field} expression, + * including: + *
NULL values.* NOTE: When inserting plain SQL into jOOQ objects, you must * guarantee syntax integrity. You may also create the possibility of