| Access | Constructor and Description |
|---|---|
| public |
| Modifier and Type | Method and Description |
|---|---|
| public boolean | bindLimitParametersInReverseOrder()
Overrides org. |
| public char | closeQuote()
Overrides org. |
| public boolean | dropConstraints()
Do we need to drop constraints before dropping tables in this dialect?
|
| public boolean | forUpdateOfColumns()
Is FOR UPDATE OF syntax supported?
|
| public String | getAddColumnString()
The syntax used to add a column to a table (optional).
|
| public String | getCreateSequenceString(String
The name of the sequence sequenceName)Overrides org. |
| public String | getCurrentTimestampSelectString()
Overrides org. |
| public String | getDropSequenceString(String
The name of the sequence sequenceName)Overrides org. |
| public String | getForUpdateString()
Get the string to append to SELECT statements to acquire locks
for this dialect.
|
| protected String | getIdentityColumnString()
Overrides org. |
| public String | getIdentitySelectString(String
The table into which the insert was done table, String The PK column. column, int The type)java. type code.Overrides org. |
| public String | getLimitString(String
The query to which to apply the limit. sql, boolean Is the query requesting an offset? hasOffset)Overrides org. |
| public String | getQuerySequencesString()
Overrides org. |
| public String | getSequenceNextValString(String
the name of the sequence sequenceName)Overrides org. |
| public boolean | hasAlterTable()
Overrides org. |
| public boolean | isCurrentTimestampSelectStringCallable()
Overrides org. getCurrentTimestampSelectString
be treated as callable.
|
| public char | openQuote()
Overrides org. |
| public boolean | |
| public boolean | supportsCurrentTimestampSelection()
Overrides org. |
| public boolean | supportsLimit()
Overrides org. |
| public boolean | supportsSequences()
Does this dialect support sequences?
|
| public boolean | supportsTemporaryTables()
Overrides org. |
| public boolean | supportsUnionAll()
Does this dialect support UNION ALL, which is generally a faster
variant of UNION?
|
| public boolean | useMaxForLimit()
Overrides org. |
| CUBRIDDialect | back to summary |
|---|---|
| public CUBRIDDialect() | |
| bindLimitParametersInReverseOrder | back to summary |
|---|---|
| public boolean bindLimitParametersInReverseOrder() Overrides org. Doc from org. ANSI SQL defines the LIMIT clause to be in the form LIMIT offset, limit. Does this dialect require us to bind the parameters in reverse order?
| |
| closeQuote | back to summary |
|---|---|
| public char closeQuote() Overrides org. Doc from org. The character specific to this dialect used to close a quoted identifier.
| |
| dropConstraints | back to summary |
|---|---|
| public boolean dropConstraints() Overrides org. Doc from org. Do we need to drop constraints before dropping tables in this dialect?
| |
| forUpdateOfColumns | back to summary |
|---|---|
| public boolean forUpdateOfColumns() Overrides org. Doc from org. Is FOR UPDATE OF syntax supported?
| |
| getAddColumnString | back to summary |
|---|---|
| public String getAddColumnString() Overrides org. Doc from org. The syntax used to add a column to a table (optional).
| |
| getCreateSequenceString | back to summary |
|---|---|
| public String getCreateSequenceString(String sequenceName) Overrides org. Doc from org. Typically dialects which support sequences can create a sequence
with a single command. This is convenience form of
Dialects which support sequences and can create a sequence in a
single command need *only* override this method. Dialects
which support sequences but require multiple commands to create
a sequence should instead override | |
| getCurrentTimestampSelectString | back to summary |
|---|---|
| public String getCurrentTimestampSelectString() Overrides org. Doc from org. Retrieve the command used to retrieve the current timestamp from the database.
| |
| getDropSequenceString | back to summary |
|---|---|
| public String getDropSequenceString(String sequenceName) Overrides org. Doc from org. Typically dialects which support sequences can drop a sequence
with a single command. This is convenience form of
Dialects which support sequences and can drop a sequence in a
single command need *only* override this method. Dialects
which support sequences but require multiple commands to drop
a sequence should instead override | |
| getForUpdateString | back to summary |
|---|---|
| public String getForUpdateString() Overrides org. Doc from org. Get the string to append to SELECT statements to acquire locks for this dialect.
| |
| getIdentityColumnString | back to summary |
|---|---|
| protected String getIdentityColumnString() throws MappingException Overrides org. Doc from org. The syntax used during DDL to define a column as being an IDENTITY.
| |
| getIdentitySelectString | back to summary |
|---|---|
| public String getIdentitySelectString(String table, String column, int type) throws MappingException Overrides org. Doc from org. Get the select command to use to retrieve the last generated IDENTITY value for a particular table
| |
| getLimitString | back to summary |
|---|---|
| public String getLimitString(String sql, boolean hasOffset) Overrides org. Doc from org. Apply s limit clause to the query.
Typically dialects utilize
Here we do still pass along whether or not an offset was specified
so that dialects not supporting offsets can generate proper exceptions.
In general, dialects will override one or the other of this method and
| |
| getQuerySequencesString | back to summary |
|---|---|
| public String getQuerySequencesString() Overrides org. Doc from org. Get the select command used retrieve the names of all sequences.
| |
| getSequenceNextValString | back to summary |
|---|---|
| public String getSequenceNextValString(String sequenceName) Overrides org. Doc from org. Generate the appropriate select statement to to retrieve the next value of a sequence. This should be a "stand alone" select statement. | |
| hasAlterTable | back to summary |
|---|---|
| public boolean hasAlterTable() Overrides org. Doc from org. Does this dialect support the ALTER TABLE syntax?
| |
| isCurrentTimestampSelectStringCallable | back to summary |
|---|---|
| public boolean isCurrentTimestampSelectStringCallable() Overrides org. Doc from org. Should the value returned by
| |
| openQuote | back to summary |
|---|---|
| public char openQuote() Overrides org. Doc from org. The character specific to this dialect used to begin a quoted identifier.
| |
| supportsCommentOn | back to summary |
|---|---|
| public boolean supportsCommentOn() | |
| supportsCurrentTimestampSelection | back to summary |
|---|---|
| public boolean supportsCurrentTimestampSelection() Overrides org. Doc from org. Does this dialect support a way to retrieve the database's current timestamp value?
| |
| supportsLimit | back to summary |
|---|---|
| public boolean supportsLimit() Overrides org. Doc from org. Does this dialect support some form of limiting query results via a SQL clause?
| |
| supportsSequences | back to summary |
|---|---|
| public boolean supportsSequences() Overrides org. Doc from org. Does this dialect support sequences?
| |
| supportsTemporaryTables | back to summary |
|---|---|
| public boolean supportsTemporaryTables() Overrides org. Doc from org. Does this dialect support temporary tables?
| |
| supportsUnionAll | back to summary |
|---|---|
| public boolean supportsUnionAll() Overrides org. Doc from org. Does this dialect support UNION ALL, which is generally a faster variant of UNION?
| |
| useMaxForLimit | back to summary |
|---|---|
| public boolean useMaxForLimit() Overrides org. Doc from org. Does the LIMIT clause take a "maximum" row number instead of a total number of returned rows? This is easiest understood via an example. Consider you have a table with 20 rows, but you only want to retrieve rows number 11 through 20. Generally, a limit with offset would say that the offset = 11 and the limit = 10 (we only want 10 rows at a time); this is specifying the total number of returned rows. Some dialects require that we instead specify offset = 11 and limit = 20, where 20 is the "last" row we want relative to offset (i.e. total number of rows = 20 - 11 = 9) So essentially, is limit relative from offset? Or is limit absolute?
| |