org.verdictdb.sqlsyntax

Class RedshiftSyntax

java.lang.Object

org.verdictdb.sqlsyntax.SqlSyntax

org.verdictdb.sqlsyntax.RedshiftSyntax

public class RedshiftSyntax
extends SqlSyntax

Constructor Summary

Constructors

Constructor and Description
RedshiftSyntax()

Method Summary

Modifier and Type	Method and Description
boolean	doesSupportTablePartitioning()
void	dropTable(String schema, String tablename)
boolean	equals(Object obj)
Collection<String>	getCandidateJDBCDriverClassNames() The drivers returned by methods are loaded explicitly by JdbcConnection (when it makes a JDBC connection to the backend database.) This mechanism is to support legacy library that does not support automatic JDBC driver discovery.
int	getColumnNameColumnIndex()
String	getColumnsCommand(String schema, String table)
int	getColumnTypeColumnIndex()
String	getFallbackDefaultSchema()
String	getPartitionByInCreateTable() Documentation about SORTKEY: https://docs.aws.amazon.com/redshift/latest/dg/r_CREATE_TABLE_NEW.html
String	getPartitionCommand(String schema, String table)
String	getQuoteString()
String	getSchemaCommand()
int	getSchemaNameColumnIndex()
String	getTableCommand(String schema)
int	getTableNameColumnIndex()
boolean	isAsRequiredBeforeSelectInCreateTable()
String	randFunction()

Methods inherited from class org.verdictdb.sqlsyntax.SqlSyntax

getStddevPopulationFunctionName, quoteName, substituteTypeName

Methods inherited from class java.lang.Object

clone, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

RedshiftSyntax

public RedshiftSyntax()

Method Detail

doesSupportTablePartitioning

public boolean doesSupportTablePartitioning()

Specified by:

doesSupportTablePartitioning in class SqlSyntax

dropTable

public void dropTable(String schema,
                      String tablename)

Specified by:

dropTable in class SqlSyntax

equals

public boolean equals(Object obj)

Overrides:

equals in class Object

getCandidateJDBCDriverClassNames

public Collection<String> getCandidateJDBCDriverClassNames()

Description copied from class: SqlSyntax

The drivers returned by methods are loaded explicitly by JdbcConnection (when it makes a JDBC connection to the backend database.) This mechanism is to support legacy library that does not support automatic JDBC driver discovery.

Overrides:

getCandidateJDBCDriverClassNames in class SqlSyntax

Returns:

getColumnNameColumnIndex

public int getColumnNameColumnIndex()

Specified by:

getColumnNameColumnIndex in class SqlSyntax

getColumnsCommand

public String getColumnsCommand(String schema,
                                String table)

Specified by:

getColumnsCommand in class SqlSyntax

getColumnTypeColumnIndex

public int getColumnTypeColumnIndex()

Specified by:

getColumnTypeColumnIndex in class SqlSyntax

getFallbackDefaultSchema

public String getFallbackDefaultSchema()

Overrides:

getFallbackDefaultSchema in class SqlSyntax

getPartitionByInCreateTable

public String getPartitionByInCreateTable()

Documentation about SORTKEY: https://docs.aws.amazon.com/redshift/latest/dg/r_CREATE_TABLE_NEW.html

If you do not specify any sort keys, the table is not sorted by default. You can define a maximum of 400 COMPOUND SORTKEY columns or 8 INTERLEAVED SORTKEY columns per table.

COMPOUND Specifies that the data is sorted using a compound key made up of all of the listed columns, in the order they are listed. A compound sort key is most useful when a query scans rows according to the order of the sort columns. The performance benefits of sorting with a compound key decrease when queries rely on secondary sort columns. You can define a maximum of 400 COMPOUND SORTKEY columns per table.

INTERLEAVED Specifies that the data is sorted using an interleaved sort key. A maximum of eight columns can be specified for an interleaved sort key.

An interleaved sort gives equal weight to each column, or subset of columns, in the sort key, so queries do not depend on the order of the columns in the sort key. When a query uses one or more secondary sort columns, interleaved sorting significantly improves query performance. Interleaved sorting carries a small overhead cost for data loading and vacuuming operations.

Important

Don’t use an interleaved sort key on columns with monotonically increasing attributes, such as identity columns, dates, or timestamps.

Specified by:

getPartitionByInCreateTable in class SqlSyntax

getPartitionCommand

public String getPartitionCommand(String schema,
                                  String table)

Specified by:

getPartitionCommand in class SqlSyntax

getQuoteString

public String getQuoteString()

Specified by:

getQuoteString in class SqlSyntax

getSchemaCommand

public String getSchemaCommand()

Specified by:

getSchemaCommand in class SqlSyntax

getSchemaNameColumnIndex

public int getSchemaNameColumnIndex()

Specified by:

getSchemaNameColumnIndex in class SqlSyntax

getTableCommand

public String getTableCommand(String schema)

Specified by:

getTableCommand in class SqlSyntax

getTableNameColumnIndex

public int getTableNameColumnIndex()

Specified by:

getTableNameColumnIndex in class SqlSyntax

isAsRequiredBeforeSelectInCreateTable

public boolean isAsRequiredBeforeSelectInCreateTable()

Specified by:

isAsRequiredBeforeSelectInCreateTable in class SqlSyntax

randFunction

public String randFunction()

Specified by:

randFunction in class SqlSyntax