Table (jOOQ 3.0.1 API)

Type Parameters:
R - The record type associated with this table

All Superinterfaces:

QueryPart, Serializable, TableLike<R>

All Known Subinterfaces:

TableOnConditionStep, TableOptionalOnStep

All Known Implementing Classes:

CustomTable, TableImpl
```
public interface Table<R extends Record>
extends TableLike<R>
```
A table to be used in queries

Author:

Lukas Eder

Method Summary

Methods
Modifier and Type	Method and Description
`Table<R>`	`as(String alias)` Create an alias for this table Note that the case-sensitivity of the returned table depends on `Settings.getRenderNameStyle()`.
`Table<R>`	`as(String alias, String... fieldAliases)` Create an alias for this table and its fields Note that the case-sensitivity of the returned table and columns depends on `Settings.getRenderNameStyle()`.
`Table<Record>`	`crossJoin(String sql)` `CROSS JOIN` a table to this table.
`Table<Record>`	`crossJoin(String sql, Object... bindings)` `CROSS JOIN` a table to this table.
`Table<Record>`	`crossJoin(String sql, QueryPart... parts)` `CROSS JOIN` a table to this table.
`Table<Record>`	`crossJoin(TableLike<?> table)` `CROSS JOIN` a table to this table.
`DivideByOnStep`	`divideBy(Table<?> divisor)` Create a new `TABLE` reference from this table, applying relational division.
`TableOnStep`	`fullOuterJoin(String sql)` `FULL OUTER JOIN` a table to this table.
`TableOnStep`	`fullOuterJoin(String sql, Object... bindings)` `FULL OUTER JOIN` a table to this table.
`TableOnStep`	`fullOuterJoin(String sql, QueryPart... parts)` `FULL OUTER JOIN` a table to this table.
`TableOnStep`	`fullOuterJoin(TableLike<?> table)` `FULL OUTER JOIN` a table to this table.
`Identity<R,? extends Number>`	`getIdentity()` Retrieve the table's `IDENTITY` information, if available.
`List<UniqueKey<R>>`	`getKeys()` Retrieve all of the table's unique keys.
`String`	`getName()` The name of this table
`UniqueKey<R>`	`getPrimaryKey()` Retrieve the table's primary key
`TableField<R,? extends Date>`	`getRecordTimestamp()` A "timestamp" field holding record timestamp information used for optimistic locking jOOQ supports optimistic locking in `UpdatableRecord.store()` and `UpdatableRecord.delete()` if `Settings.isExecuteWithOptimisticLocking()` is enabled.
`Class<? extends R>`	`getRecordType()`
`TableField<R,? extends Number>`	`getRecordVersion()` A "version" field holding record version information used for optimistic locking jOOQ supports optimistic locking in `UpdatableRecord.store()` and `UpdatableRecord.delete()` if `Settings.isExecuteWithOptimisticLocking()` is enabled.
`List<ForeignKey<R,?>>`	`getReferences()` Get the list of `FOREIGN KEY`'s of this table
`<O extends Record> List<ForeignKey<O,R>>`	`getReferencesFrom(Table<O> other)` Get a list of `FOREIGN KEY`'s of a specific table, referencing a this table.
`<O extends Record> List<ForeignKey<R,O>>`	`getReferencesTo(Table<O> other)` Get a list of `FOREIGN KEY`'s of this table, referencing a specific table.
`Schema`	`getSchema()` Get the table schema
`TableOnStep`	`join(String sql)` `INNER JOIN` a table to this table.
`TableOnStep`	`join(String sql, Object... bindings)` `INNER JOIN` a table to this table.
`TableOnStep`	`join(String sql, QueryPart... parts)` `INNER JOIN` a table to this table.
`TableOnStep`	`join(TableLike<?> table)` `INNER JOIN` a table to this table.
`TableOptionalOnStep`	`join(TableLike<?> table, JoinType type)` Join a table to this table using a `JoinType` Depending on the `JoinType`, a subsequent `TableOnStep.on(Condition...)` or `TableOnStep.using(Field...)` clause is required.
`TablePartitionByStep`	`leftOuterJoin(String sql)` `LEFT OUTER JOIN` a table to this table.
`TablePartitionByStep`	`leftOuterJoin(String sql, Object... bindings)` `LEFT OUTER JOIN` a table to this table.
`TablePartitionByStep`	`leftOuterJoin(String sql, QueryPart... parts)` `LEFT OUTER JOIN` a table to this table.
`TablePartitionByStep`	`leftOuterJoin(TableLike<?> table)` `LEFT OUTER JOIN` a table to this table.
`Table<Record>`	`naturalJoin(String sql)` `NATURAL JOIN` a table to this table.
`Table<Record>`	`naturalJoin(String sql, Object... bindings)` `NATURAL JOIN` a table to this table.
`Table<Record>`	`naturalJoin(String sql, QueryPart... parts)` `NATURAL JOIN` a table to this table.
`Table<Record>`	`naturalJoin(TableLike<?> table)` `NATURAL JOIN` a table to this table.
`Table<Record>`	`naturalLeftOuterJoin(String sql)` `NATURAL LEFT OUTER JOIN` a table to this table.
`Table<Record>`	`naturalLeftOuterJoin(String sql, Object... bindings)` `NATURAL LEFT OUTER JOIN` a table to this table.
`Table<Record>`	`naturalLeftOuterJoin(String sql, QueryPart... parts)` `NATURAL LEFT OUTER JOIN` a table to this table.
`Table<Record>`	`naturalLeftOuterJoin(TableLike<?> table)` `NATURAL LEFT OUTER JOIN` a table to this table.
`Table<Record>`	`naturalRightOuterJoin(String sql)` `NATURAL RIGHT OUTER JOIN` a table to this table.
`Table<Record>`	`naturalRightOuterJoin(String sql, Object... bindings)` `NATURAL RIGHT OUTER JOIN` a table to this table.
`Table<Record>`	`naturalRightOuterJoin(String sql, QueryPart... parts)` `NATURAL RIGHT OUTER JOIN` a table to this table.
`Table<Record>`	`naturalRightOuterJoin(TableLike<?> table)` `NATURAL RIGHT OUTER JOIN` a table to this table.
`PivotForStep`	`pivot(Collection<? extends Field<?>> aggregateFunctions)` Create a new `TABLE` reference from this table, pivoting it into another form For more details, see `pivot(Field...)`
`PivotForStep`	`pivot(Field<?>... aggregateFunctions)` Create a new `TABLE` reference from this table, pivoting it into another form This has been observed to work with `SQLDialect.ORACLE` `SQLDialect.SQLSERVER` (not yet officially supported) Other dialects by using some means of simulation (not yet officially supported)
`TablePartitionByStep`	`rightOuterJoin(String sql)` `RIGHT OUTER JOIN` a table to this table.
`TablePartitionByStep`	`rightOuterJoin(String sql, Object... bindings)` `RIGHT OUTER JOIN` a table to this table.
`TablePartitionByStep`	`rightOuterJoin(String sql, QueryPart... parts)` `RIGHT OUTER JOIN` a table to this table.
`TablePartitionByStep`	`rightOuterJoin(TableLike<?> table)` `RIGHT OUTER JOIN` a table to this table.
`Table<R>`	`with(String hint)` Specify a SQL Server style table hint for query optimisation This makes sense only on an actual database table or view, not on other composed table sources.

Methods inherited from interface org.jooq.TableLike
asTable, asTable, asTable, field, field, field, fields, fieldsRow

Methods inherited from interface org.jooq.QueryPart
equals, hashCode, toString

- Method Detail
  - getSchema
```
Schema getSchema()
```
    Get the table schema
  - getName
```
String getName()
```
    The name of this table
  - getRecordType
```
Class<? extends R> getRecordType()
```
    Returns:
    The record type produced by this table
  - as
```
@Support
Table<R> as(String alias)
```
    Create an alias for this table
    Note that the case-sensitivity of the returned table depends on Settings.getRenderNameStyle(). By default, table aliases are quoted, and thus case-sensitive!
    
    Parameters:
    alias - The alias name
    
    Returns:
    The table alias
  - as
```
@Support
Table<R> as(String alias,
                  String... fieldAliases)
```
    Create an alias for this table and its fields
    Note that the case-sensitivity of the returned table and columns depends on Settings.getRenderNameStyle(). By default, table aliases are quoted, and thus case-sensitive!
    
    Derived column lists for table references
    
    Note, not all databases support derived column lists for their table aliases. On the other hand, some databases do support derived column lists, but only for derived tables. jOOQ will try to turn table references into derived tables to make this syntax work. In other words, the following statements are equivalent:
```
 -- Using derived column lists to rename columns (e.g. Postgres)
 SELECT t.a, t.b
 FROM my_table t(a, b)

 -- Nesting table references within derived tables (e.g. SQL Server)
 SELECT t.a, t.b
 FROM (
   SELECT * FROM my_table
 ) t(a, b)
 
```
    Derived column lists for derived tables
    
    Other databases may not support derived column lists at all, but they do support common table expressions. The following statements are equivalent:
```
 -- Using derived column lists to rename columns (e.g. Postgres)
 SELECT t.a, t.b
 FROM (
   SELECT 1, 2
 ) AS t(a, b)

 -- Using UNION ALL to produce column names (e.g. MySQL)
 SELECT t.a, t.b
 FROM (
   SELECT null a, null b FROM DUAL WHERE 1 = 0
   UNION ALL
   SELECT 1, 2 FROM DUAL
 ) t
 
```
    Parameters:
    alias - The alias name
    fieldAliases - The field aliases. Excess aliases are ignored, missing aliases will be substituted by this table's field names.
    
    Returns:
    The table alias
  - getIdentity
```
Identity<R,? extends Number> getIdentity()
```
    Retrieve the table's IDENTITY information, if available.
    With SQL:2003, the concept of IDENTITY columns was introduced in most RDBMS. These are special kinds of columns that have auto-increment functionality when INSERT statements are performed.
    An IDENTITY column is usually part of the PRIMARY KEY or of a UNIQUE KEY in the table, although in some RDBMS, this is not required. There can only be at most one IDENTITY column.
    Note: Unfortunately, this is not supported in the Oracle dialect, where identities simulated by triggers cannot be formally detected.
    
    Returns:
    The table's IDENTITY information, or null, if no such information is available.
  - getPrimaryKey
```
UniqueKey<R> getPrimaryKey()
```
    Retrieve the table's primary key
    
    Returns:
    The primary key. This is never null for an updatable table.
  - getRecordVersion
```
TableField<R,? extends Number> getRecordVersion()
```
    A "version" field holding record version information used for optimistic locking
    jOOQ supports optimistic locking in UpdatableRecord.store() and UpdatableRecord.delete() if Settings.isExecuteWithOptimisticLocking() is enabled. Optimistic locking is performed in a single UPDATE or DELETE statement if tables provide a "version" or "timestamp" field, or in two steps using an additional SELECT .. FOR UPDATE statement otherwise.
    This method is overridden in generated subclasses if their corresponding tables have been configured accordingly. A table may have both a "version" and a "timestamp" field.
    
    Returns:
    The "version" field, or null, if this table has no "version" field.
    See Also:
    getRecordTimestamp(), UpdatableRecord.store(), UpdatableRecord.delete(), Settings.isExecuteWithOptimisticLocking()
  - getRecordTimestamp
```
TableField<R,? extends Date> getRecordTimestamp()
```
    A "timestamp" field holding record timestamp information used for optimistic locking
    jOOQ supports optimistic locking in UpdatableRecord.store() and UpdatableRecord.delete() if Settings.isExecuteWithOptimisticLocking() is enabled. Optimistic locking is performed in a single UPDATE or DELETE statement if tables provide a "version" or "timestamp" field, or in two steps using an additional SELECT .. FOR UPDATE statement otherwise.
    This method is overridden in generated subclasses if their corresponding tables have been configured accordingly. A table may have both a "version" and a "timestamp" field.
    
    Returns:
    The "timestamp" field, or null, if this table has no "timestamp" field.
    See Also:
    getRecordVersion(), UpdatableRecord.store(), UpdatableRecord.delete(), Settings.isExecuteWithOptimisticLocking()
  - getKeys
```
List<UniqueKey<R>> getKeys()
```
    Retrieve all of the table's unique keys.
    
    Returns:
    All keys. This is never null. This is never empty for a Table with a getPrimaryKey(). This method returns an unmodifiable list.
  - getReferencesFrom
```
<O extends Record> List<ForeignKey<O,R>> getReferencesFrom(Table<O> other)
```
    Get a list of FOREIGN KEY's of a specific table, referencing a this table.
    
    Type Parameters:
    O - The other table's record type
    Parameters:
    other - The other table of the foreign key relationship
    
    Returns:
    Some other table's FOREIGN KEY's towards an this table. This is never null. This method returns an unmodifiable list.
  - getReferences
```
List<ForeignKey<R,?>> getReferences()
```
    Get the list of FOREIGN KEY's of this table
    
    Returns:
    This table's FOREIGN KEY's. This is never null.
  - getReferencesTo
```
<O extends Record> List<ForeignKey<R,O>> getReferencesTo(Table<O> other)
```
    Get a list of FOREIGN KEY's of this table, referencing a specific table.
    
    Type Parameters:
    O - The other table's record type
    Parameters:
    other - The other table of the foreign key relationship
    
    Returns:
    This table's FOREIGN KEY's towards an other table. This is never null.
  - with
```
@Support(value={SQLSERVER,SYBASE})
Table<R> with(String hint)
```
    Specify a SQL Server style table hint for query optimisation
    This makes sense only on an actual database table or view, not on other composed table sources.
    Example:
```
 create.select()
       .from(BOOK.as("b").with("READUNCOMMITTED")
       .fetch();
 
```
    For SQLDialect.ORACLE style hints, see SelectFromStep.hint(String) and SelectQuery.addHint(String)
    See Also:
    http://msdn.microsoft.com/en-us/library/ms187373.aspx, SelectFromStep.hint(String), SelectQuery.addHint(String)
  - pivot
```
@Support(value=ORACLE)
PivotForStep pivot(Field<?>... aggregateFunctions)
```
    Create a new TABLE reference from this table, pivoting it into another form
    This has been observed to work with
    - SQLDialect.ORACLE
    - SQLDialect.SQLSERVER (not yet officially supported)
    - Other dialects by using some means of simulation (not yet officially supported)
    Parameters:
    aggregateFunctions - The aggregate functions used for pivoting.
    
    Returns:
    A DSL object to create the PIVOT expression
  - pivot
```
@Support(value=ORACLE)
PivotForStep pivot(Collection<? extends Field<?>> aggregateFunctions)
```
    Create a new TABLE reference from this table, pivoting it into another form
    For more details, see pivot(Field...)
    
    Parameters:
    aggregateFunctions - The aggregate functions used for pivoting.
    
    Returns:
    A DSL object to create the PIVOT expression
    See Also:
    pivot(Field...)
  - divideBy
```
@Support
DivideByOnStep divideBy(Table<?> divisor)
```
    Create a new TABLE reference from this table, applying relational division.
    Relational division is the inverse of a cross join operation. The following is an approximate definition of a relational division:
```
 Assume the following cross join / cartesian product
 C = A × B

 Then it can be said that
 A = C ÷ B
 B = C ÷ A
 
```
    With jOOQ, you can simplify using relational divisions by using the following syntax:
```
 C.divideBy(B).on(C.ID.equal(B.C_ID)).returning(C.TEXT)
 
```
    The above roughly translates to
```
 SELECT DISTINCT C.TEXT FROM C "c1"
 WHERE NOT EXISTS (
   SELECT 1 FROM B
   WHERE NOT EXISTS (
     SELECT 1 FROM C "c2"
     WHERE "c2".TEXT = "c1".TEXT
     AND "c2".ID = B.C_ID
   )
 )
 
```
    Or in plain text: Find those TEXT values in C whose ID's correspond to all ID's in B. Note that from the above SQL statement, it is immediately clear that proper indexing is of the essence. Be sure to have indexes on all columns referenced from the on(...) and returning(...) clauses.
    For more information about relational division and some nice, real-life examples, see
    - http ://en.wikipedia.org/wiki/Relational_algebra#Division
    - http://www.simple-talk.com/sql/t-sql-programming/divided-we-stand-the- sql-of-relational-division/
    This has been observed to work with all dialects
  - join
```
@Support
TableOptionalOnStep join(TableLike<?> table,
                               JoinType type)
```
    Join a table to this table using a JoinType
    Depending on the JoinType, a subsequent TableOnStep.on(Condition...) or TableOnStep.using(Field...) clause is required. If it is required but omitted, a DSL.trueCondition(), i.e. 1 = 1 condition will be rendered
  - join
```
@Support
TableOnStep join(TableLike<?> table)
```
    INNER JOIN a table to this table.
  - join
```
@Support
TableOnStep join(String sql)
```
    INNER JOIN a table to this table.
    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!
    
    See Also:
    DSL.table(String)
  - join
```
@Support
TableOnStep join(String sql,
                       Object... bindings)
```
    INNER JOIN a table to this table.
    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!
    
    See Also:
    DSL.table(String, Object...)
  - join
```
@Support
TableOnStep join(String sql,
                       QueryPart... parts)
```
    INNER JOIN a table to this table.
    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!
    
    See Also:
    DSL.table(String, QueryPart...)
  - leftOuterJoin
```
@Support
TablePartitionByStep leftOuterJoin(TableLike<?> table)
```
    LEFT OUTER JOIN a table to this table.
  - leftOuterJoin
```
@Support
TablePartitionByStep leftOuterJoin(String sql)
```
    LEFT OUTER JOIN a table to this table.
    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!
    
    See Also:
    DSL.table(String)
  - leftOuterJoin
```
@Support
TablePartitionByStep leftOuterJoin(String sql,
                                         Object... bindings)
```
    LEFT OUTER JOIN a table to this table.
    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!
    
    See Also:
    DSL.table(String, Object...)
  - leftOuterJoin
```
@Support
TablePartitionByStep leftOuterJoin(String sql,
                                         QueryPart... parts)
```
    LEFT OUTER JOIN a table to this table.
    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!
    
    See Also:
    DSL.table(String, QueryPart...)
  - rightOuterJoin
```
@Support(value={ASE,CUBRID,DB2,DERBY,FIREBIRD,H2,HSQLDB,INGRES,MYSQL,ORACLE,POSTGRES,SQLSERVER,SYBASE})
TablePartitionByStep rightOuterJoin(TableLike<?> table)
```
    RIGHT OUTER JOIN a table to this table.
    This is only possible where the underlying RDBMS supports it
  - rightOuterJoin
```
@Support(value={ASE,CUBRID,DB2,DERBY,FIREBIRD,H2,HSQLDB,INGRES,MYSQL,ORACLE,POSTGRES,SQLSERVER,SYBASE})
TablePartitionByStep rightOuterJoin(String sql)
```
    RIGHT OUTER JOIN a table to this table.
    This is only possible where the underlying RDBMS supports it
    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!
    
    See Also:
    DSL.table(String)
  - rightOuterJoin
```
@Support(value={ASE,CUBRID,DB2,DERBY,FIREBIRD,H2,HSQLDB,INGRES,MYSQL,ORACLE,POSTGRES,SQLSERVER,SYBASE})
TablePartitionByStep rightOuterJoin(String sql,
                                                                                                                        Object... bindings)
```
    RIGHT OUTER JOIN a table to this table.
    This is only possible where the underlying RDBMS supports it
    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!
    
    See Also:
    DSL.table(String, Object...)
  - rightOuterJoin
```
@Support(value={ASE,CUBRID,DB2,DERBY,FIREBIRD,H2,HSQLDB,INGRES,MYSQL,ORACLE,POSTGRES,SQLSERVER,SYBASE})
TablePartitionByStep rightOuterJoin(String sql,
                                                                                                                        QueryPart... parts)
```
    RIGHT OUTER JOIN a table to this table.
    This is only possible where the underlying RDBMS supports it
    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!
    
    See Also:
    DSL.table(String, QueryPart...)
  - fullOuterJoin
```
@Support(value={DB2,FIREBIRD,HSQLDB,INGRES,ORACLE,POSTGRES,SQLSERVER,SYBASE})
TableOnStep fullOuterJoin(TableLike<?> table)
```
    FULL OUTER JOIN a table to this table.
    This is only possible where the underlying RDBMS supports it
  - fullOuterJoin
```
@Support(value={DB2,FIREBIRD,HSQLDB,INGRES,ORACLE,POSTGRES,SQLSERVER,SYBASE})
TableOnStep fullOuterJoin(String sql)
```
    FULL OUTER JOIN a table to this table.
    This is only possible where the underlying RDBMS supports it
    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!
    
    See Also:
    DSL.table(String)
  - fullOuterJoin
```
@Support(value={DB2,FIREBIRD,HSQLDB,INGRES,ORACLE,POSTGRES,SQLSERVER,SYBASE})
TableOnStep fullOuterJoin(String sql,
                                                                                         Object... bindings)
```
    FULL OUTER JOIN a table to this table.
    This is only possible where the underlying RDBMS supports it
    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!
    
    See Also:
    DSL.table(String, Object...)
  - fullOuterJoin
```
@Support(value={DB2,FIREBIRD,HSQLDB,INGRES,ORACLE,POSTGRES,SQLSERVER,SYBASE})
TableOnStep fullOuterJoin(String sql,
                                                                                         QueryPart... parts)
```
    FULL OUTER JOIN a table to this table.
    This is only possible where the underlying RDBMS supports it
    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!
    
    See Also:
    DSL.table(String, QueryPart...)
  - crossJoin
```
@Support
Table<Record> crossJoin(TableLike<?> table)
```
    CROSS JOIN a table to this table.
    If this syntax is unavailable, it is simulated with a regular INNER JOIN. The following two constructs are equivalent:
```
 A cross join B
 A join B on 1 = 1
 
```
  - crossJoin
```
@Support
Table<Record> crossJoin(String sql)
```
    CROSS JOIN a table to this table.
    If this syntax is unavailable, it is simulated with a regular INNER JOIN. The following two constructs are equivalent:
```
 A cross join B
 A join B on 1 = 1
 
```
    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!
    See Also:
    DSL.table(String)
  - crossJoin
```
@Support
Table<Record> crossJoin(String sql,
                              Object... bindings)
```
    CROSS JOIN a table to this table.
    If this syntax is unavailable, it is simulated with a regular INNER JOIN. The following two constructs are equivalent:
```
 A cross join B
 A join B on 1 = 1
 
```
    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!
    See Also:
    DSL.table(String, Object...)
  - crossJoin
```
@Support
Table<Record> crossJoin(String sql,
                              QueryPart... parts)
```
    CROSS JOIN a table to this table.
    If this syntax is unavailable, it is simulated with a regular INNER JOIN. The following two constructs are equivalent:
```
 A cross join B
 A join B on 1 = 1
 
```
    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!
    See Also:
    DSL.table(String, QueryPart...)
  - naturalJoin
```
@Support
Table<Record> naturalJoin(TableLike<?> table)
```
    NATURAL JOIN a table to this table.
    If this is not supported by your RDBMS, then jOOQ will try to simulate this behaviour using the information provided in this query.
  - naturalJoin
```
@Support
Table<Record> naturalJoin(String sql)
```
    NATURAL JOIN a table to this table.
    If this is not supported by your RDBMS, then jOOQ will try to simulate this behaviour using the information provided in this query.
    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!
    
    See Also:
    DSL.table(String)
  - naturalJoin
```
@Support
Table<Record> naturalJoin(String sql,
                                Object... bindings)
```
    NATURAL JOIN a table to this table.
    If this is not supported by your RDBMS, then jOOQ will try to simulate this behaviour using the information provided in this query.
    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!
    
    See Also:
    DSL.table(String, Object...)
  - naturalJoin
```
@Support
Table<Record> naturalJoin(String sql,
                                QueryPart... parts)
```
    NATURAL JOIN a table to this table.
    If this is not supported by your RDBMS, then jOOQ will try to simulate this behaviour using the information provided in this query.
    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!
    
    See Also:
    DSL.table(String, QueryPart...)
  - naturalLeftOuterJoin
```
@Support
Table<Record> naturalLeftOuterJoin(TableLike<?> table)
```
    NATURAL LEFT OUTER JOIN a table to this table.
    If this is not supported by your RDBMS, then jOOQ will try to simulate this behaviour using the information provided in this query.
  - naturalLeftOuterJoin
```
@Support
Table<Record> naturalLeftOuterJoin(String sql)
```
    NATURAL LEFT OUTER JOIN a table to this table.
    If this is not supported by your RDBMS, then jOOQ will try to simulate this behaviour using the information provided in this query.
    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!
    
    See Also:
    DSL.table(String)
  - naturalLeftOuterJoin
```
@Support
Table<Record> naturalLeftOuterJoin(String sql,
                                         Object... bindings)
```
    NATURAL LEFT OUTER JOIN a table to this table.
    If this is not supported by your RDBMS, then jOOQ will try to simulate this behaviour using the information provided in this query.
    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!
    
    See Also:
    DSL.table(String, Object...)
  - naturalLeftOuterJoin
```
@Support
Table<Record> naturalLeftOuterJoin(String sql,
                                         QueryPart... parts)
```
    NATURAL LEFT OUTER JOIN a table to this table.
    If this is not supported by your RDBMS, then jOOQ will try to simulate this behaviour using the information provided in this query.
    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!
    
    See Also:
    DSL.table(String, QueryPart...)
  - naturalRightOuterJoin
```
@Support(value={ASE,CUBRID,DB2,DERBY,FIREBIRD,H2,HSQLDB,INGRES,MYSQL,ORACLE,POSTGRES,SQLSERVER,SYBASE})
Table<Record> naturalRightOuterJoin(TableLike<?> table)
```
    NATURAL RIGHT OUTER JOIN a table to this table.
    If this is not supported by your RDBMS, then jOOQ will try to simulate this behaviour using the information provided in this query.
  - naturalRightOuterJoin
```
@Support(value={ASE,CUBRID,DB2,DERBY,FIREBIRD,H2,HSQLDB,INGRES,MYSQL,ORACLE,POSTGRES,SQLSERVER,SYBASE})
Table<Record> naturalRightOuterJoin(String sql)
```
    NATURAL RIGHT OUTER JOIN a table to this table.
    If this is not supported by your RDBMS, then jOOQ will try to simulate this behaviour using the information provided in this query.
    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!
    
    See Also:
    DSL.table(String)
  - naturalRightOuterJoin
```
@Support(value={ASE,CUBRID,DB2,DERBY,FIREBIRD,H2,HSQLDB,INGRES,MYSQL,ORACLE,POSTGRES,SQLSERVER,SYBASE})
Table<Record> naturalRightOuterJoin(String sql,
                                                                                                                        Object... bindings)
```
    NATURAL RIGHT OUTER JOIN a table to this table.
    If this is not supported by your RDBMS, then jOOQ will try to simulate this behaviour using the information provided in this query.
    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!
    
    See Also:
    DSL.table(String, Object...)
  - naturalRightOuterJoin
```
@Support(value={ASE,CUBRID,DB2,DERBY,FIREBIRD,H2,HSQLDB,INGRES,MYSQL,ORACLE,POSTGRES,SQLSERVER,SYBASE})
Table<Record> naturalRightOuterJoin(String sql,
                                                                                                                        QueryPart... parts)
```
    NATURAL RIGHT OUTER JOIN a table to this table.
    If this is not supported by your RDBMS, then jOOQ will try to simulate this behaviour using the information provided in this query.
    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!
    
    See Also:
    DSL.table(String, QueryPart...)

Interface Table<R extends Record>

Method Summary

Methods inherited from interface org.jooq.TableLike

Methods inherited from interface org.jooq.QueryPart

Method Detail

getSchema

getName

getRecordType

as

as

Derived column lists for table references

Derived column lists for derived tables

getIdentity

getPrimaryKey

getRecordVersion

getRecordTimestamp

getKeys

getReferencesFrom

getReferences

getReferencesTo

with

pivot

pivot

divideBy

join

join

join

join

join

leftOuterJoin

leftOuterJoin

leftOuterJoin

leftOuterJoin

rightOuterJoin

rightOuterJoin

rightOuterJoin

rightOuterJoin

fullOuterJoin

fullOuterJoin

fullOuterJoin

fullOuterJoin

crossJoin

crossJoin

crossJoin

crossJoin

naturalJoin

naturalJoin

naturalJoin

naturalJoin

naturalLeftOuterJoin

naturalLeftOuterJoin

naturalLeftOuterJoin

naturalLeftOuterJoin

naturalRightOuterJoin

naturalRightOuterJoin

naturalRightOuterJoin

naturalRightOuterJoin