[jOOQ/jOOQ#15602] Plain SQL Javadoc disclaimer is absent on api

generator generated step methods
This commit is contained in:
Lukas Eder 2023-09-15 11:55:47 +02:00
parent b7e0e04e99
commit de1195b669
3 changed files with 60 additions and 60 deletions

View File

@ -100,11 +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!
* <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
*/
@ -115,11 +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!
* <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,11 +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!
* <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
*/
@ -145,11 +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!
* <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
*/

View File

@ -72,11 +72,6 @@ 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.
@ -107,6 +102,11 @@ public interface CreateTableStorageStep extends CreateTableFinalStep {
* escape literals when concatenated into SQL clauses! One way to escape
* literals is to use {@link DSL#name(String...)} and similar methods
* 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!
*
* @see SQL
*/
@ -117,11 +117,6 @@ 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 +147,11 @@ public interface CreateTableStorageStep extends CreateTableFinalStep {
* escape literals when concatenated into SQL clauses! One way to escape
* literals is to use {@link DSL#name(String...)} and similar methods
* 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!
*
* @see SQL
*/
@ -162,11 +162,6 @@ 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.
@ -197,6 +192,11 @@ public interface CreateTableStorageStep extends CreateTableFinalStep {
* escape literals when concatenated into SQL clauses! One way to escape
* literals is to use {@link DSL#name(String...)} and similar methods
* 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!
*
* @see SQL
*/
@ -207,11 +207,6 @@ 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.
@ -242,6 +237,11 @@ public interface CreateTableStorageStep extends CreateTableFinalStep {
* escape literals when concatenated into SQL clauses! One way to escape
* literals is to use {@link DSL#name(String...)} and similar methods
* 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!
*
* @see SQL
*/

View File

@ -79,11 +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!
* <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
*/
@ -94,11 +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!
* <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,11 +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!
* <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
*/
@ -124,11 +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!
* <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
*/