java.lang.Object
- org.hibernate.dialect.Dialect
- - org.hibernate.dialect.H2Dialect

所有已实现的接口:

ConversionContext
```
public class H2Dialect
extends Dialect
```
A dialect compatible with the H2 database.

作者:

Thomas Mueller

字段概要
- 从类继承的字段 org.hibernate.dialect.Dialect
  CLOSED_QUOTE, DEFAULT_BATCH_SIZE, LEGACY_LOB_MERGE_STRATEGY, NEW_LOCATOR_LOB_MERGE_STRATEGY, NO_BATCH, QUOTE, STANDARD_DEFAULT_BATCH_LOAD_SIZING_STRATEGY, STREAM_XFER_LOB_MERGE_STRATEGY, TWO_SINGLE_QUOTES_REPLACEMENT

构造器概要

构造器
构造器说明

H2Dialect()
Constructs a H2Dialect

方法概要

所有方法实例方法具体方法
修饰符和类型	方法	说明
`boolean`	`bindLimitParametersFirst()`	Does the `LIMIT` clause come at the start of the `SELECT` statement, rather than at the end?
`boolean`	`bindLimitParametersInReverseOrder()`	ANSI SQL defines the LIMIT clause to be in the form LIMIT offset, limit.
`SQLExceptionConversionDelegate`	`buildSQLExceptionConversionDelegate()`	Build an instance of a `SQLExceptionConversionDelegate` for interpreting dialect-specific error or SQLState codes.
`boolean`	`doesReadCommittedCauseWritersToBlockReaders()`	For the underlying database, is READ_COMMITTED isolation implemented by forcing readers to wait for write locks to be released?
`boolean`	`dropConstraints()`	Do we need to drop constraints before dropping tables in this dialect?
`String`	`getAddColumnString()`	The syntax used to add a column to a table (optional).
`String`	`getCreateSequenceString(String sequenceName)`	Typically dialects which support sequences can create a sequence with a single command.
`String`	`getCurrentTimestampSelectString()`	Retrieve the command used to retrieve the current timestamp from the database.
`MultiTableBulkIdStrategy`	`getDefaultMultiTableBulkIdStrategy()`
`String`	`getDropSequenceString(String sequenceName)`	Typically dialects which support sequences can drop a sequence with a single command.
`String`	`getForUpdateString()`	Get the string to append to SELECT statements to acquire locks for this dialect.
`IdentityColumnSupport`	`getIdentityColumnSupport()`	Get the appropriate `IdentityColumnSupport`
`LimitHandler`	`getLimitHandler()`	Returns the delegate managing LIMIT clause.
`String`	`getLimitString(String sql, boolean hasOffset)`	Apply a limit clause to the query.
`String`	`getQueryHintString(String query, String hints)`	Apply a hint to the query.
`String`	`getQuerySequencesString()`	Get the select command used retrieve the names of all sequences.
`String`	`getSelectSequenceNextValString(String sequenceName)`	Generate the select expression fragment that will retrieve the next value of a sequence as part of another (typically DML) statement.
`SequenceInformationExtractor`	`getSequenceInformationExtractor()`
`String`	`getSequenceNextValString(String sequenceName)`	Generate the appropriate select statement to to retrieve the next value of a sequence.
`ViolatedConstraintNameExtracter`	`getViolatedConstraintNameExtracter()`
`boolean`	`isCurrentTimestampSelectStringCallable()`	Should the value returned by `Dialect.getCurrentTimestampSelectString()` be treated as callable.
`boolean`	`requiresParensForTupleDistinctCounts()`	If `Dialect.supportsTupleDistinctCounts()` is true, does the Dialect require the tuple to be wrapped with parens?
`boolean`	`supportsCurrentTimestampSelection()`	Does this dialect support a way to retrieve the database's current timestamp value?
`boolean`	`supportsIfExistsAfterTableName()`	For dropping a table, can the phrase "if exists" be applied after the table name?
`boolean`	`supportsIfExistsBeforeConstraintName()`	For dropping a constraint with an "alter table", can the phrase "if exists" be applied before the constraint name?
`boolean`	`supportsLimit()`	Does this dialect support some form of limiting query results via a SQL clause?
`boolean`	`supportsLobValueChangePropogation()`	Does the dialect support propagating changes to LOB values back to the database?
`boolean`	`supportsPooledSequences()`	Does this dialect support "pooled" sequences.
`boolean`	`supportsSelectAliasInGroupByClause()`
`boolean`	`supportsSequences()`	Does this dialect support sequences?
`boolean`	`supportsTuplesInSubqueries()`	Does this dialect support tuples in subqueries?
`boolean`	`supportsUnionAll()`	Does this dialect support UNION ALL, which is generally a faster variant of UNION?

从类继承的方法 org.hibernate.dialect.Dialect
addSqlHintOrComment, appendLockHint, appendLockHint, applyLocksToSql, areStringComparisonsCaseInsensitive, augmentRecognizedTableTypes, buildIdentifierHelper, buildSQLExceptionConverter, canCreateCatalog, canCreateSchema, cast, cast, cast, closeQuote, contributeTypes, convertToFirstRowValue, createCaseFragment, createOuterJoinFragment, defaultScrollMode, doesRepeatableReadCauseReadersToBlockWriters, escapeLiteral, forceLimitUsage, forceLobAsLastValue, forUpdateOfColumns, getAddColumnSuffixString, getAddForeignKeyConstraintString, getAddForeignKeyConstraintString, getAddPrimaryKeyConstraintString, getAddUniqueConstraintString, getAlterTableString, getAuxiliaryDatabaseObjectExporter, getCallableStatementSupport, getCascadeConstraintsString, getCaseInsensitiveLike, getCastTypeName, getColumnAliasExtractor, getColumnComment, getCreateCatalogCommand, getCreateMultisetTableString, getCreateSchemaCommand, getCreateSequenceString, getCreateSequenceStrings, getCreateSequenceStrings, getCreateTableString, getCrossJoinSeparator, getCurrentSchemaCommand, getCurrentTimestampSQLFunctionName, getDefaultBatchLoadSizingStrategy, getDefaultProperties, getDialect, getDialect, getDropCatalogCommand, getDropForeignKeyString, getDropSchemaCommand, getDropSequenceStrings, getDropTableString, getForeignKeyExporter, getForUpdateNowaitString, getForUpdateNowaitString, getForUpdateSkipLockedString, getForUpdateSkipLockedString, getForUpdateString, getForUpdateString, getForUpdateString, getForUpdateString, getFunctions, getHibernateTypeName, getHibernateTypeName, getIndexExporter, getInExpressionCountLimit, getKeywords, getLimitString, getLobMergeStrategy, getLockingStrategy, getLowercaseFunction, getMaxAliasLength, getNameQualifierSupport, getNativeIdentifierGeneratorClass, getNativeIdentifierGeneratorStrategy, getNoColumnsInsertString, getNotExpression, getNullColumnString, getQueryHintString, getReadLockString, getReadLockString, getResultSet, getResultSet, getResultSet, getSchemaNameResolver, getSelectClauseNullString, getSelectGUIDString, getSequenceExporter, getSqlTypeDescriptorOverride, getTableComment, getTableExporter, getTableTypeString, getTypeName, getTypeName, getUniqueDelegate, getUniqueKeyExporter, getWriteLockString, getWriteLockString, hasAlterTable, hasSelfReferentialForeignKeyBug, inlineLiteral, isJdbcLogWarningsEnabledByDefault, isLegacyLimitHandlerBehaviorEnabled, isLockTimeoutParameterized, isTypeNameRegistered, openQuote, prependComment, qualifyIndexName, quote, registerColumnType, registerColumnType, registerFunction, registerHibernateType, registerHibernateType, registerKeyword, registerResultSetOutParameter, registerResultSetOutParameter, remapSqlTypeDescriptor, renderOrderByElement, replaceResultVariableInOrderByClauseWithPosition, requiresCastingOfParametersInSelectClause, supportsBindAsCallableArgument, supportsCascadeDelete, supportsCaseInsensitiveLike, supportsCircularCascadeDeleteConstraints, supportsColumnCheck, supportsCommentOn, supportsEmptyInList, supportsExistsInSelect, supportsExpectedLobUsagePattern, supportsIfExistsAfterAlterTable, supportsIfExistsAfterConstraintName, supportsIfExistsBeforeTableName, supportsJdbcConnectionLobCreation, supportsLimitOffset, supportsLockTimeouts, supportsNamedParameters, supportsNationalizedTypes, supportsNoColumnsInsert, supportsNonQueryWithCTE, supportsNotNullUnique, supportsNoWait, supportsOuterJoinForUpdate, supportsParametersInInsertSelect, supportsPartitionBy, supportsResultSetPositionQueryMethodsOnForwardOnlyCursor, supportsRowValueConstructorSyntax, supportsRowValueConstructorSyntaxInInList, supportsSkipLocked, supportsSubqueryOnMutatingTable, supportsSubselectAsInPredicateLHS, supportsTableCheck, supportsTupleCounts, supportsTupleDistinctCounts, supportsUnboundedLobLocatorMaterialization, supportsUnique, supportsUniqueConstraintInCreateAlterTable, supportsValuesList, supportsVariableLimit, toBooleanValueString, toString, transformSelectString, useFollowOnLocking, useFollowOnLocking, useInputStreamToInsertBlob, useMaxForLimit

从类继承的方法 java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait

- 构造器详细资料
  - H2Dialect
```
public H2Dialect()
```
    Constructs a H2Dialect
- 方法详细资料
  - getAddColumnString
```
public String getAddColumnString()
```
    从类复制的说明: Dialect
    
    The syntax used to add a column to a table (optional).
    
    覆盖:
    
    getAddColumnString 在类中 Dialect
    
    返回:
    
    The "add column" fragment.
  - getForUpdateString
```
public String getForUpdateString()
```
    从类复制的说明: Dialect
    
    Get the string to append to SELECT statements to acquire locks for this dialect.
    
    覆盖:
    
    getForUpdateString 在类中 Dialect
    
    返回:
    
    The appropriate FOR UPDATE clause string.
  - getLimitHandler
```
public LimitHandler getLimitHandler()
```
    从类复制的说明: Dialect
    
    Returns the delegate managing LIMIT clause.
    
    覆盖:
    
    getLimitHandler 在类中 Dialect
    
    返回:
    
    LIMIT clause delegate.
  - supportsLimit
```
public boolean supportsLimit()
```
    从类复制的说明: Dialect
    
    Does this dialect support some form of limiting query results via a SQL clause?
    
    覆盖:
    
    supportsLimit 在类中 Dialect
    
    返回:
    
    True if this dialect supports some form of LIMIT.
  - getLimitString
```
public String getLimitString(String sql,
                             boolean hasOffset)
```
    从类复制的说明: Dialect
    
    Apply a limit clause to the query.
    Typically dialects utilize variable limit clauses when they support limits. Thus, when building the select command we do not actually need to know the limit or the offset since we will just be using placeholders.
    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 Dialect.getLimitString(String, int, int).
    
    覆盖:
    
    getLimitString 在类中 Dialect
    
    参数:
    
    sql - The query to which to apply the limit.
    
    hasOffset - Is the query requesting an offset?
    
    返回:
    
    the modified SQL
  - bindLimitParametersInReverseOrder
```
public boolean bindLimitParametersInReverseOrder()
```
    从类复制的说明: Dialect
    
    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?
    
    覆盖:
    
    bindLimitParametersInReverseOrder 在类中 Dialect
    
    返回:
    
    true if the correct order is limit, offset
  - bindLimitParametersFirst
```
public boolean bindLimitParametersFirst()
```
    从类复制的说明: Dialect
    
    Does the LIMIT clause come at the start of the SELECT statement, rather than at the end?
    
    覆盖:
    
    bindLimitParametersFirst 在类中 Dialect
    
    返回:
    
    true if limit parameters should come before other parameters
  - supportsIfExistsAfterTableName
```
public boolean supportsIfExistsAfterTableName()
```
    从类复制的说明: Dialect
    
    For dropping a table, can the phrase "if exists" be applied after the table name?
    NOTE : Only one or the other (or neither) of this and Dialect.supportsIfExistsBeforeTableName() should return true
    
    覆盖:
    
    supportsIfExistsAfterTableName 在类中 Dialect
    
    返回:
    
    true if the "if exists" can be applied after the table name
  - supportsIfExistsBeforeConstraintName
```
public boolean supportsIfExistsBeforeConstraintName()
```
    从类复制的说明: Dialect
    
    For dropping a constraint with an "alter table", can the phrase "if exists" be applied before the constraint name?
    NOTE : Only one or the other (or neither) of this and Dialect.supportsIfExistsAfterConstraintName() should return true
    
    覆盖:
    
    supportsIfExistsBeforeConstraintName 在类中 Dialect
    
    返回:
    
    true if the "if exists" can be applied before the constraint name
  - supportsSequences
```
public boolean supportsSequences()
```
    从类复制的说明: Dialect
    
    Does this dialect support sequences?
    
    覆盖:
    
    supportsSequences 在类中 Dialect
    
    返回:
    
    True if sequences supported; false otherwise.
  - supportsPooledSequences
```
public boolean supportsPooledSequences()
```
    从类复制的说明: Dialect
    
    Does this dialect support "pooled" sequences. Not aware of a better name for this. Essentially can we specify the initial and increment values?
    
    覆盖:
    
    supportsPooledSequences 在类中 Dialect
    
    返回:
    
    True if such "pooled" sequences are supported; false otherwise.
    
    另请参阅:
    
    Dialect.getCreateSequenceStrings(String, int, int), Dialect.getCreateSequenceString(String, int, int)
  - getCreateSequenceString
```
public String getCreateSequenceString(String sequenceName)
```
    从类复制的说明: Dialect
    
    Typically dialects which support sequences can create a sequence with a single command. This is convenience form of Dialect.getCreateSequenceStrings(java.lang.String) to help facilitate that.
    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 Dialect.getCreateSequenceStrings(java.lang.String).
    
    覆盖:
    
    getCreateSequenceString 在类中 Dialect
    
    参数:
    
    sequenceName - The name of the sequence
    
    返回:
    
    The sequence creation command
  - getDropSequenceString
```
public String getDropSequenceString(String sequenceName)
```
    从类复制的说明: Dialect
    
    Typically dialects which support sequences can drop a sequence with a single command. This is convenience form of Dialect.getDropSequenceStrings(java.lang.String) to help facilitate that.
    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 Dialect.getDropSequenceStrings(java.lang.String).
    
    覆盖:
    
    getDropSequenceString 在类中 Dialect
    
    参数:
    
    sequenceName - The name of the sequence
    
    返回:
    
    The sequence drop commands
  - getSelectSequenceNextValString
```
public String getSelectSequenceNextValString(String sequenceName)
```
    从类复制的说明: Dialect
    
    Generate the select expression fragment that will retrieve the next value of a sequence as part of another (typically DML) statement.
    This differs from Dialect.getSequenceNextValString(String) in that this should return an expression usable within another statement.
    
    覆盖:
    
    getSelectSequenceNextValString 在类中 Dialect
    
    参数:
    
    sequenceName - the name of the sequence
    
    返回:
    
    The "nextval" fragment.
  - getSequenceNextValString
```
public String getSequenceNextValString(String sequenceName)
```
    从类复制的说明: Dialect
    
    Generate the appropriate select statement to to retrieve the next value of a sequence.
    This should be a "stand alone" select statement.
    
    覆盖:
    
    getSequenceNextValString 在类中 Dialect
    
    参数:
    
    sequenceName - the name of the sequence
    
    返回:
    
    String The "nextval" select string.
  - getQuerySequencesString
```
public String getQuerySequencesString()
```
    从类复制的说明: Dialect
    
    Get the select command used retrieve the names of all sequences.
    
    覆盖:
    
    getQuerySequencesString 在类中 Dialect
    
    返回:
    
    The select command; or null if sequences are not supported.
    
    另请参阅:
    
    SchemaUpdate
  - getSequenceInformationExtractor
```
public SequenceInformationExtractor getSequenceInformationExtractor()
```
    覆盖:
    
    getSequenceInformationExtractor 在类中 Dialect
  - getViolatedConstraintNameExtracter
```
public ViolatedConstraintNameExtracter getViolatedConstraintNameExtracter()
```
    指定者:
    
    getViolatedConstraintNameExtracter 在接口中 ConversionContext
    
    覆盖:
    
    getViolatedConstraintNameExtracter 在类中 Dialect
  - buildSQLExceptionConversionDelegate
```
public SQLExceptionConversionDelegate buildSQLExceptionConversionDelegate()
```
    从类复制的说明: Dialect
    Build an instance of a SQLExceptionConversionDelegate for interpreting dialect-specific error or SQLState codes.
    When Dialect.buildSQLExceptionConverter() returns null, the default SQLExceptionConverter is used to interpret SQLState and error codes. If this method is overridden to return a non-null value, the default SQLExceptionConverter will use the returned SQLExceptionConversionDelegate in addition to the following standard delegates:
    
    a "static" delegate based on the JDBC 4 defined SQLException hierarchy;
    
    a delegate that interprets SQLState codes for either X/Open or SQL-2003 codes, depending on java.sql.DatabaseMetaData#getSQLStateType
    
    It is strongly recommended that specific Dialect implementations override this method, since interpretation of a SQL error is much more accurate when based on the vendor-specific ErrorCode rather than the SQLState.
    Specific Dialects may override to return whatever is most appropriate for that vendor.
    覆盖:
    
    buildSQLExceptionConversionDelegate 在类中 Dialect
    
    返回:
    
    The SQLExceptionConversionDelegate for this dialect
  - getDefaultMultiTableBulkIdStrategy
```
public MultiTableBulkIdStrategy getDefaultMultiTableBulkIdStrategy()
```
    覆盖:
    
    getDefaultMultiTableBulkIdStrategy 在类中 Dialect
  - supportsCurrentTimestampSelection
```
public boolean supportsCurrentTimestampSelection()
```
    从类复制的说明: Dialect
    
    Does this dialect support a way to retrieve the database's current timestamp value?
    
    覆盖:
    
    supportsCurrentTimestampSelection 在类中 Dialect
    
    返回:
    
    True if the current timestamp can be retrieved; false otherwise.
  - isCurrentTimestampSelectStringCallable
```
public boolean isCurrentTimestampSelectStringCallable()
```
    从类复制的说明: Dialect
    
    Should the value returned by Dialect.getCurrentTimestampSelectString() be treated as callable. Typically this indicates that JDBC escape syntax is being used...
    
    覆盖:
    
    isCurrentTimestampSelectStringCallable 在类中 Dialect
    
    返回:
    
    True if the Dialect.getCurrentTimestampSelectString() return is callable; false otherwise.
  - getCurrentTimestampSelectString
```
public String getCurrentTimestampSelectString()
```
    从类复制的说明: Dialect
    
    Retrieve the command used to retrieve the current timestamp from the database.
    
    覆盖:
    
    getCurrentTimestampSelectString 在类中 Dialect
    
    返回:
    
    The command.
  - supportsUnionAll
```
public boolean supportsUnionAll()
```
    从类复制的说明: Dialect
    
    Does this dialect support UNION ALL, which is generally a faster variant of UNION?
    
    覆盖:
    
    supportsUnionAll 在类中 Dialect
    
    返回:
    
    True if UNION ALL is supported; false otherwise.
  - supportsLobValueChangePropogation
```
public boolean supportsLobValueChangePropogation()
```
    从类复制的说明: Dialect
    
    Does the dialect support propagating changes to LOB values back to the database? Talking about mutating the internal value of the locator as opposed to supplying a new locator instance...
    For BLOBs, the internal value might be changed by: Blob.setBinaryStream(long), Blob.setBytes(long, byte[]), Blob.setBytes(long, byte[], int, int), or Blob.truncate(long).
    For CLOBs, the internal value might be changed by: Clob.setAsciiStream(long), Clob.setCharacterStream(long), Clob.setString(long, String), Clob.setString(long, String, int, int), or Clob.truncate(long).
    NOTE : I do not know the correct answer currently for databases which (1) are not part of the cruise control process or (2) do not Dialect.supportsExpectedLobUsagePattern().
    
    覆盖:
    
    supportsLobValueChangePropogation 在类中 Dialect
    
    返回:
    
    True if the changes are propagated back to the database; false otherwise.
  - requiresParensForTupleDistinctCounts
```
public boolean requiresParensForTupleDistinctCounts()
```
    从类复制的说明: Dialect
    
    If Dialect.supportsTupleDistinctCounts() is true, does the Dialect require the tuple to be wrapped with parens?
    
    覆盖:
    
    requiresParensForTupleDistinctCounts 在类中 Dialect
    
    返回:
    
    boolean
  - doesReadCommittedCauseWritersToBlockReaders
```
public boolean doesReadCommittedCauseWritersToBlockReaders()
```
    从类复制的说明: Dialect
    
    For the underlying database, is READ_COMMITTED isolation implemented by forcing readers to wait for write locks to be released?
    
    覆盖:
    
    doesReadCommittedCauseWritersToBlockReaders 在类中 Dialect
    
    返回:
    
    True if writers block readers to achieve READ_COMMITTED; false otherwise.
  - supportsTuplesInSubqueries
```
public boolean supportsTuplesInSubqueries()
```
    从类复制的说明: Dialect
    
    Does this dialect support tuples in subqueries? Ex: delete from Table1 where (col1, col2) in (select col1, col2 from Table2)
    
    覆盖:
    
    supportsTuplesInSubqueries 在类中 Dialect
    
    返回:
    
    boolean
  - dropConstraints
```
public boolean dropConstraints()
```
    从类复制的说明: Dialect
    
    Do we need to drop constraints before dropping tables in this dialect?
    
    覆盖:
    
    dropConstraints 在类中 Dialect
    
    返回:
    
    True if constraints must be dropped prior to dropping the table; false otherwise.
  - getIdentityColumnSupport
```
public IdentityColumnSupport getIdentityColumnSupport()
```
    从类复制的说明: Dialect
    
    Get the appropriate IdentityColumnSupport
    
    覆盖:
    
    getIdentityColumnSupport 在类中 Dialect
    
    返回:
    
    the IdentityColumnSupport
  - getQueryHintString
```
public String getQueryHintString(String query,
                                 String hints)
```
    从类复制的说明: Dialect
    
    Apply a hint to the query. The entire query is provided, allowing the Dialect full control over the placement and syntax of the hint. By default, ignore the hint and simply return the query.
    
    覆盖:
    
    getQueryHintString 在类中 Dialect
    
    参数:
    
    query - The query to which to apply the hint.
    
    hints - The hints to apply
    
    返回:
    
    The modified SQL
  - supportsSelectAliasInGroupByClause
```
public boolean supportsSelectAliasInGroupByClause()
```
    覆盖:
    
    supportsSelectAliasInGroupByClause 在类中 Dialect

类 H2Dialect

字段概要

从类继承的字段 org.hibernate.dialect.Dialect

构造器概要

方法概要

从类继承的方法 org.hibernate.dialect.Dialect

从类继承的方法 java.lang.Object

构造器详细资料

H2Dialect

方法详细资料

getAddColumnString

getForUpdateString

getLimitHandler

supportsLimit

getLimitString

bindLimitParametersInReverseOrder

bindLimitParametersFirst

supportsIfExistsAfterTableName

supportsIfExistsBeforeConstraintName

supportsSequences

supportsPooledSequences

getCreateSequenceString

getDropSequenceString

getSelectSequenceNextValString

getSequenceNextValString

getQuerySequencesString

getSequenceInformationExtractor

getViolatedConstraintNameExtracter

buildSQLExceptionConversionDelegate

getDefaultMultiTableBulkIdStrategy

supportsCurrentTimestampSelection

isCurrentTimestampSelectStringCallable

getCurrentTimestampSelectString

supportsUnionAll

supportsLobValueChangePropogation

requiresParensForTupleDistinctCounts

doesReadCommittedCauseWritersToBlockReaders

supportsTuplesInSubqueries

dropConstraints

getIdentityColumnSupport

getQueryHintString

supportsSelectAliasInGroupByClause