Module org.jooq
Package org.jooq

Interface CreateTableStorageStep

    • Method Detail

      • storage

        @Support
        @PlainSQL
        CreateTableFinalStep storage​(SQL sql)
        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

        Parameters:
        sql - The SQL
      • storage

        @Support
        @PlainSQL
        CreateTableFinalStep storage​(String sql)
        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

        Parameters:
        sql - The SQL
      • storage

        @Support
        @PlainSQL
        CreateTableFinalStep storage​(String sql,
                                     Object... bindings)
        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

        Parameters:
        sql - The SQL
        bindings - The bindings
      • storage

        @Support
        @PlainSQL
        CreateTableFinalStep storage​(String sql,
                                     QueryPart... parts)
        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

        Parameters:
        sql - The SQL
        parts - The QueryPart objects that are rendered at the {numbered placeholder} locations