github/jooq
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[jOOQ/jOOQ#15602] Plain SQL Javadoc disclaimer is absent on api generator generated step methods

Browse Source
This commit is contained in:
Lukas Eder 2023-09-15 11:45:37 +02:00
parent 89276bfc3f
commit b7e0e04e99
4 changed files with 80 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
jOOQ/src/main/java/org/jooq/CreateIndexWhereStep.java
View File

@ -100,6 +100,11 @@ public interface CreateIndexWhereStep extends CreateIndexFinalStep {
/**
* Add the <code>WHERE</code> clause to the <code>CREATE INDEX</code> statement.
<p>
<b>NOTE</b>: When inserting plain SQL into jOOQ objects, you must
guarantee syntax integrity. You may also create the possibility of
malicious SQL injection. Be sure to properly use bind variables and/or
escape literals when concatenated into SQL clauses!
*
* @see SQL
*/
@ -110,6 +115,11 @@ public interface CreateIndexWhereStep extends CreateIndexFinalStep {
/**
* Add the <code>WHERE</code> clause to the <code>CREATE INDEX</code> statement.
<p>
<b>NOTE</b>: When inserting plain SQL into jOOQ objects, you must
guarantee syntax integrity. You may also create the possibility of
malicious SQL injection. Be sure to properly use bind variables and/or
escape literals when concatenated into SQL clauses!
*
* @see SQL
*/
@ -120,6 +130,11 @@ public interface CreateIndexWhereStep extends CreateIndexFinalStep {
/**
* Add the <code>WHERE</code> clause to the <code>CREATE INDEX</code> statement.
<p>
<b>NOTE</b>: When inserting plain SQL into jOOQ objects, you must
guarantee syntax integrity. You may also create the possibility of
malicious SQL injection. Be sure to properly use bind variables and/or
escape literals when concatenated into SQL clauses!
*
* @see SQL
*/
@ -130,6 +145,11 @@ public interface CreateIndexWhereStep extends CreateIndexFinalStep {
/**
* Add the <code>WHERE</code> clause to the <code>CREATE INDEX</code> statement.
<p>
<b>NOTE</b>: When inserting plain SQL into jOOQ objects, you must
guarantee syntax integrity. You may also create the possibility of
malicious SQL injection. Be sure to properly use bind variables and/or
escape literals when concatenated into SQL clauses!
*
* @see SQL
*/

20
jOOQ/src/main/java/org/jooq/CreateTableStorageStep.java
View File

@ -72,6 +72,11 @@ public interface CreateTableStorageStep extends CreateTableFinalStep {
/**
* Add the <code>STORAGE</code> clause to the <code>CREATE TABLE</code> statement.
<p>
<b>NOTE</b>: When inserting plain SQL into jOOQ objects, you must
guarantee syntax integrity. You may also create the possibility of
malicious SQL injection. Be sure to properly use bind variables and/or
escape literals when concatenated into SQL clauses!
* <p>
* Add vendor-specific storage clauses to the <code>CREATE TABLE</code>
* statement.
@ -112,6 +117,11 @@ public interface CreateTableStorageStep extends CreateTableFinalStep {
/**
* Add the <code>STORAGE</code> clause to the <code>CREATE TABLE</code> statement.
<p>
<b>NOTE</b>: When inserting plain SQL into jOOQ objects, you must
guarantee syntax integrity. You may also create the possibility of
malicious SQL injection. Be sure to properly use bind variables and/or
escape literals when concatenated into SQL clauses!
* <p>
* Add vendor-specific storage clauses to the <code>CREATE TABLE</code>
* statement.
@ -152,6 +162,11 @@ public interface CreateTableStorageStep extends CreateTableFinalStep {
/**
* Add the <code>STORAGE</code> clause to the <code>CREATE TABLE</code> statement.
<p>
<b>NOTE</b>: When inserting plain SQL into jOOQ objects, you must
guarantee syntax integrity. You may also create the possibility of
malicious SQL injection. Be sure to properly use bind variables and/or
escape literals when concatenated into SQL clauses!
* <p>
* Add vendor-specific storage clauses to the <code>CREATE TABLE</code>
* statement.
@ -192,6 +207,11 @@ public interface CreateTableStorageStep extends CreateTableFinalStep {
/**
* Add the <code>STORAGE</code> clause to the <code>CREATE TABLE</code> statement.
<p>
<b>NOTE</b>: When inserting plain SQL into jOOQ objects, you must
guarantee syntax integrity. You may also create the possibility of
malicious SQL injection. Be sure to properly use bind variables and/or
escape literals when concatenated into SQL clauses!
* <p>
* Add vendor-specific storage clauses to the <code>CREATE TABLE</code>
* statement.

20
jOOQ/src/main/java/org/jooq/CreateTriggerWhenStep.java
View File

@ -123,6 +123,26 @@ package org.jooq;

20
jOOQ/src/main/java/org/jooq/CreateViewAsStep.java
View File

@ -79,6 +79,11 @@ public interface CreateViewAsStep<R extends Record> {
/**
* Add the <code>AS</code> clause to the <code>CREATE VIEW</code> statement.
<p>
<b>NOTE</b>: When inserting plain SQL into jOOQ objects, you must
guarantee syntax integrity. You may also create the possibility of
malicious SQL injection. Be sure to properly use bind variables and/or
escape literals when concatenated into SQL clauses!
*
* @see SQL
*/
@ -89,6 +94,11 @@ public interface CreateViewAsStep<R extends Record> {
/**
* Add the <code>AS</code> clause to the <code>CREATE VIEW</code> statement.
<p>
<b>NOTE</b>: When inserting plain SQL into jOOQ objects, you must
guarantee syntax integrity. You may also create the possibility of
malicious SQL injection. Be sure to properly use bind variables and/or
escape literals when concatenated into SQL clauses!
*
* @see SQL
*/
@ -99,6 +109,11 @@ public interface CreateViewAsStep<R extends Record> {
/**
* Add the <code>AS</code> clause to the <code>CREATE VIEW</code> statement.
<p>
<b>NOTE</b>: When inserting plain SQL into jOOQ objects, you must
guarantee syntax integrity. You may also create the possibility of
malicious SQL injection. Be sure to properly use bind variables and/or
escape literals when concatenated into SQL clauses!
*
* @see SQL
*/
@ -109,6 +124,11 @@ public interface CreateViewAsStep<R extends Record> {
/**
* Add the <code>AS</code> clause to the <code>CREATE VIEW</code> statement.
<p>
<b>NOTE</b>: When inserting plain SQL into jOOQ objects, you must
guarantee syntax integrity. You may also create the possibility of
malicious SQL injection. Be sure to properly use bind variables and/or
escape literals when concatenated into SQL clauses!
*
* @see SQL
*/