When working with SQL, strings are ubiquitous. They can have different meanings, in the jOOQ API. A string can be:
org.jooq.Param )org.jooq.SQL )org.jooq.Name )org.jooq.Keyword )org.jooq.Comment While the jOOQ API applies conventions consistently, it may not always be clear which convention applies. Keywords are hardly a problem, but beginners often confuse when jOOQ offers plain SQL templates for convenience (arbitrary SQL fragments, usually not case-sensitive, SQL injection prone), or identifiers (often case-sensitive, depending on the dialect).
The annotations in this class are used to document each of these stringly typed API elements to make the semantics more clear. For increased clarity, the stringly-typed convenience API can always be avoided in favour of the more strongly-typed API.
| Modifier and Type | Class and Description |
|---|---|
| public static @interface | Stringly.Comment
The annotated string type represents a keyword |
| public static @interface | Stringly.Keyword
The annotated string type represents a keyword |
| public static @interface | Stringly.Name
The annotated string type represents an identifier, i.e. a
|
| public static @interface | Stringly.Param
The annotated string type represents a bind variable, i.e. a
|
| public static @interface | Stringly.SQL
The annotated string type represents a plain SQL template, i.e. a
|
| Access | Constructor and Description |
|---|---|
| public |
| Stringly | back to summary |
|---|---|
| public Stringly() | |
org.jooq.Comment ,
which will be wrapped by DSL#comment(String).
org.jooq.Keyword ,
which will be wrapped by DSL#keyword(String).
org.jooq.Name , which will be wrapped by DSL#name(String).
org.jooq.Param .
org.jooq.SQL , which will be wrapped by DSL#sql(String).