jOOQ 3.18.7 · org.jooq.CreateTableStorageStep

Modifier and Type	Method and Description
public @NotNull CreateTableFinalStep	storage(SQL storage) Deprecated as a consequence of `CreateTableFinalStep` being deprecated. Add the `STORAGE` clause to the `CREATE TABLE` statement.
public @NotNull CreateTableFinalStep	storage(String storage, QueryPart... parts) Deprecated as a consequence of `CreateTableFinalStep` being deprecated. Add the `STORAGE` clause to the `CREATE TABLE` statement.
public @NotNull CreateTableFinalStep	storage(String storage, Object... bindings) Deprecated as a consequence of `CreateTableFinalStep` being deprecated. Add the `STORAGE` clause to the `CREATE TABLE` statement.
public @NotNull CreateTableFinalStep	storage(String storage) Deprecated as a consequence of `CreateTableFinalStep` being deprecated. Add the `STORAGE` clause to the `CREATE TABLE` statement.

Method Detail

storage back to summary

storage	back to summary
public @NotNull CreateTableFinalStep storage(SQL storage) Deprecated as a consequence of `CreateTableFinalStep` being deprecated. See corresponding docs for further information. Add the `STORAGE` clause to the `CREATE TABLE` statement. Add vendor-specific storage clauses to the `CREATE TABLE` statement. Storage clauses will always be appended to the end of everything else that jOOQ renders, including possibly other storage clauses, such as `CreateTableOnCommitStep#onCommitDeleteRows()` or similar clauses. If custom storage clauses should be mixed with jOOQ-provided storage clauses, it is recommended not to use the jOOQ API and use the custom clause API for all storage clauses instead. Storage clauses will be separated from previous elements by a separator (whitespace or newline) to ensure syntactic integrity. Example usage: `DSL.using(configuration) .createTable("t") .column(field("i", SQLDataType.INTEGER)) .storage("TABLESPACE my_tablespace") .execute();` Note 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! One way to escape literals is to use `DSL#name(String...)` and similar methods Add the `STORAGE` clause to the `CREATE TABLE` statement. Note 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! Annotations @Support @PlainSQL @NotNull @CheckReturnValue See Also `SQL`

public @NotNull CreateTableFinalStep storage(SQL storage)

Deprecated

as a consequence of CreateTableFinalStep being deprecated. See corresponding docs for further information.

Add the STORAGE clause to the CREATE TABLE statement.

Add vendor-specific storage clauses to the CREATE TABLE statement.

Storage clauses will always be appended to the end of everything else that jOOQ renders, including possibly other storage clauses, such as CreateTableOnCommitStep#onCommitDeleteRows() or similar clauses. If custom storage clauses should be mixed with jOOQ-provided storage clauses, it is recommended not to use the jOOQ API and use the custom clause API for all storage clauses instead.

Storage clauses will be separated from previous elements by a separator (whitespace or newline) to ensure syntactic integrity.

Example usage:


DSL.using(configuration)
   .createTable("t")
   .column(field("i", SQLDataType.INTEGER))
   .storage("TABLESPACE my_tablespace")
   .execute();

Note

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! One way to escape literals is to use DSL#name(String...) and similar methods Add the STORAGE clause to the CREATE TABLE statement.

Note

Annotations

@Support
@PlainSQL
@NotNull
@CheckReturnValue

See Also

SQL

storage back to summary

storage	back to summary
public @NotNull CreateTableFinalStep storage(String storage, QueryPart... parts) Deprecated as a consequence of `CreateTableFinalStep` being deprecated. See corresponding docs for further information. Add the `STORAGE` clause to the `CREATE TABLE` statement. Add vendor-specific storage clauses to the `CREATE TABLE` statement. Storage clauses will always be appended to the end of everything else that jOOQ renders, including possibly other storage clauses, such as `CreateTableOnCommitStep#onCommitDeleteRows()` or similar clauses. If custom storage clauses should be mixed with jOOQ-provided storage clauses, it is recommended not to use the jOOQ API and use the custom clause API for all storage clauses instead. Storage clauses will be separated from previous elements by a separator (whitespace or newline) to ensure syntactic integrity. Example usage: `DSL.using(configuration) .createTable("t") .column(field("i", SQLDataType.INTEGER)) .storage("TABLESPACE my_tablespace") .execute();` Note 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! One way to escape literals is to use `DSL#name(String...)` and similar methods Add the `STORAGE` clause to the `CREATE TABLE` statement. Note 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! Annotations @Support @PlainSQL @NotNull @CheckReturnValue See Also `SQL`

public @NotNull CreateTableFinalStep storage(String storage, QueryPart... parts)

Deprecated

as a consequence of CreateTableFinalStep being deprecated. See corresponding docs for further information.

Add the STORAGE clause to the CREATE TABLE statement.

Add vendor-specific storage clauses to the CREATE TABLE statement.

Storage clauses will be separated from previous elements by a separator (whitespace or newline) to ensure syntactic integrity.

Example usage:


DSL.using(configuration)
   .createTable("t")
   .column(field("i", SQLDataType.INTEGER))
   .storage("TABLESPACE my_tablespace")
   .execute();

Note

Annotations

@Support
@PlainSQL
@NotNull
@CheckReturnValue

See Also

SQL

storage back to summary

storage	back to summary
public @NotNull CreateTableFinalStep storage(String storage, Object... bindings) Deprecated as a consequence of `CreateTableFinalStep` being deprecated. See corresponding docs for further information. Add the `STORAGE` clause to the `CREATE TABLE` statement. Add vendor-specific storage clauses to the `CREATE TABLE` statement. Storage clauses will always be appended to the end of everything else that jOOQ renders, including possibly other storage clauses, such as `CreateTableOnCommitStep#onCommitDeleteRows()` or similar clauses. If custom storage clauses should be mixed with jOOQ-provided storage clauses, it is recommended not to use the jOOQ API and use the custom clause API for all storage clauses instead. Storage clauses will be separated from previous elements by a separator (whitespace or newline) to ensure syntactic integrity. Example usage: `DSL.using(configuration) .createTable("t") .column(field("i", SQLDataType.INTEGER)) .storage("TABLESPACE my_tablespace") .execute();` Note 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! One way to escape literals is to use `DSL#name(String...)` and similar methods Add the `STORAGE` clause to the `CREATE TABLE` statement. Note 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! Annotations @Support @PlainSQL @NotNull @CheckReturnValue See Also `SQL`

public @NotNull CreateTableFinalStep storage(String storage, Object... bindings)

Deprecated

as a consequence of CreateTableFinalStep being deprecated. See corresponding docs for further information.

Add the STORAGE clause to the CREATE TABLE statement.

Add vendor-specific storage clauses to the CREATE TABLE statement.

Storage clauses will be separated from previous elements by a separator (whitespace or newline) to ensure syntactic integrity.

Example usage:


DSL.using(configuration)
   .createTable("t")
   .column(field("i", SQLDataType.INTEGER))
   .storage("TABLESPACE my_tablespace")
   .execute();

Note

Annotations

@Support
@PlainSQL
@NotNull
@CheckReturnValue

See Also

SQL

storage back to summary

storage	back to summary
public @NotNull CreateTableFinalStep storage(String storage) Deprecated as a consequence of `CreateTableFinalStep` being deprecated. See corresponding docs for further information. Add the `STORAGE` clause to the `CREATE TABLE` statement. Add vendor-specific storage clauses to the `CREATE TABLE` statement. Storage clauses will always be appended to the end of everything else that jOOQ renders, including possibly other storage clauses, such as `CreateTableOnCommitStep#onCommitDeleteRows()` or similar clauses. If custom storage clauses should be mixed with jOOQ-provided storage clauses, it is recommended not to use the jOOQ API and use the custom clause API for all storage clauses instead. Storage clauses will be separated from previous elements by a separator (whitespace or newline) to ensure syntactic integrity. Example usage: `DSL.using(configuration) .createTable("t") .column(field("i", SQLDataType.INTEGER)) .storage("TABLESPACE my_tablespace") .execute();` Note 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! One way to escape literals is to use `DSL#name(String...)` and similar methods Add the `STORAGE` clause to the `CREATE TABLE` statement. Note 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! Annotations @Support @PlainSQL @NotNull @CheckReturnValue See Also `SQL`

public @NotNull CreateTableFinalStep storage(String storage)

Deprecated

as a consequence of CreateTableFinalStep being deprecated. See corresponding docs for further information.

Add the STORAGE clause to the CREATE TABLE statement.

Add vendor-specific storage clauses to the CREATE TABLE statement.

Storage clauses will be separated from previous elements by a separator (whitespace or newline) to ensure syntactic integrity.

Example usage:


DSL.using(configuration)
   .createTable("t")
   .column(field("i", SQLDataType.INTEGER))
   .storage("TABLESPACE my_tablespace")
   .execute();

Note

Annotations

@Support
@PlainSQL
@NotNull
@CheckReturnValue

See Also

SQL

public Interface CreateTableStorageStep

Referencing `XYZ*Step` types directly from client code

Method Summary

Method Detail

public Interface CreateTableStorageStep

Referencing XYZ*Step types directly from client code

Method Summary

Method Detail

Referencing `XYZ*Step` types directly from client code