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

所有已实现的接口:

ConversionContext

直接已知子类:

PostgreSQL82Dialect
```
public class PostgreSQL81Dialect
extends Dialect
```
An SQL dialect for Postgres
For discussion of BLOB support in Postgres, as of 8.4, have a peek at http://jdbc.postgresql.org/documentation/84/binary-data.html. For the effects in regards to Hibernate see http://in.relation.to/15492.lace

作者:

Gavin King

字段概要
- 从类继承的字段 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

构造器概要

构造器
构造器说明

PostgreSQL81Dialect()
Constructs a PostgreSQL81Dialect

方法概要

所有方法实例方法具体方法
修饰符和类型	方法	说明
`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`	`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).
`CallableStatementSupport`	`getCallableStatementSupport()`
`String`	`getCascadeConstraintsString()`	Completely optional cascading drop clause
`String`	`getCaseInsensitiveLike()`	The name of the SQL function that can do case insensitive like comparison.
`String`	`getCreateSequenceString(String sequenceName)`	Typically dialects which support sequences can create a sequence with a single command.
`protected String`	`getCreateSequenceString(String sequenceName, int initialValue, int incrementSize)`	only necessary for postgre < 7.4 See http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/create_sequence.sgml
`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`	`getForUpdateNowaitString()`	Retrieves the `FOR UPDATE NOWAIT` syntax specific to this dialect.
`String`	`getForUpdateNowaitString(String aliases)`	Get the `FOR UPDATE OF column_list NOWAIT` fragment appropriate for this dialect given the aliases of the columns to be write locked.
`String`	`getForUpdateString()`	Get the string to append to SELECT statements to acquire locks for this dialect.
`String`	`getForUpdateString(String aliases)`	Get the `FOR UPDATE OF column_list` fragment appropriate for this dialect given the aliases of the columns to be write locked.
`String`	`getForUpdateString(String aliases, LockOptions lockOptions)`	Get the `FOR UPDATE OF column_list` fragment appropriate for this dialect given the aliases of the columns to be write locked.
`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`	`getNativeIdentifierGeneratorStrategy()`	Resolves the native generation strategy associated to this dialect.
`String`	`getNoColumnsInsertString()`	The fragment used to insert a row without specifying any column values.
`String`	`getQuerySequencesString()`	Get the select command used retrieve the names of all sequences.
`String`	`getReadLockString(int timeout)`	Get the string to append to SELECT statements to acquire READ locks for this dialect.
`String`	`getReadLockString(String aliases, int timeout)`	Get the string to append to SELECT statements to acquire READ locks for this dialect given the aliases of the columns to be read locked.
`ResultSet`	`getResultSet(CallableStatement ps)`	Given a callable statement previously processed by `Dialect.registerResultSetOutParameter(java.sql.CallableStatement, int)`, extract the `ResultSet` from the OUT parameter.
`ResultSet`	`getResultSet(CallableStatement statement, int position)`	Given a callable statement previously processed by `Dialect.registerResultSetOutParameter(java.sql.CallableStatement, int)`, extract the `ResultSet`.
`ResultSet`	`getResultSet(CallableStatement statement, String name)`	Given a callable statement previously processed by `Dialect.registerResultSetOutParameter(java.sql.CallableStatement, int)`, extract the `ResultSet` from the OUT parameter.
`String`	`getSelectClauseNullString(int sqlType)`	Workaround for postgres bug #1453
`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.
`String`	`getSequenceNextValString(String sequenceName)`	Generate the appropriate select statement to to retrieve the next value of a sequence.
`SqlTypeDescriptor`	`getSqlTypeDescriptorOverride(int sqlCode)`	Returns the `SqlTypeDescriptor` that should be used to handle the given JDBC type code.
`ViolatedConstraintNameExtracter`	`getViolatedConstraintNameExtracter()`
`String`	`getWriteLockString(int timeout)`	Get the string to append to SELECT statements to acquire WRITE locks for this dialect.
`String`	`getWriteLockString(String aliases, int timeout)`	Get the string to append to SELECT statements to acquire WRITE locks for this dialect given the aliases of the columns to be write locked.
`boolean`	`isCurrentTimestampSelectStringCallable()`	Should the value returned by `Dialect.getCurrentTimestampSelectString()` be treated as callable.
`boolean`	`qualifyIndexName()`	Do we need to qualify index names with the schema name?
`int`	`registerResultSetOutParameter(CallableStatement statement, int col)`	Registers a parameter (either OUT, or the new REF_CURSOR param type available in Java 8) capable of returning `ResultSet` by position.
`boolean`	`requiresParensForTupleDistinctCounts()`	If `Dialect.supportsTupleDistinctCounts()` is true, does the Dialect require the tuple to be wrapped with parens?
`boolean`	`supportsCaseInsensitiveLike()`	Does this dialect support case insensitive LIKE restrictions?
`boolean`	`supportsCommentOn()`	Does this dialect/database support commenting on tables, columns, etc?
`boolean`	`supportsCurrentTimestampSelection()`	Does this dialect support a way to retrieve the database's current timestamp value?
`boolean`	`supportsEmptyInList()`	Does this dialect support empty IN lists?
`boolean`	`supportsExpectedLobUsagePattern()`	Expected LOB usage pattern is such that I can perform an insert via prepared statement with a parameter binding for a LOB value without crazy casting to JDBC driver implementation-specific classes...
`boolean`	`supportsJdbcConnectionLobCreation(DatabaseMetaData databaseMetaData)`	Check whether the JDBC `Connection` supports creating LOBs via `Connection.createBlob()`, `Connection.createNClob()` or `Connection.createClob()`.
`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`	`supportsNationalizedTypes()`	Does this dialect supports Nationalized Types
`boolean`	`supportsNoWait()`	Does this dialect/database support NO_WAIT timeout.
`boolean`	`supportsOuterJoinForUpdate()`	Does this dialect support `FOR UPDATE` in conjunction with outer joined rows?
`boolean`	`supportsPooledSequences()`	Does this dialect support "pooled" sequences.
`boolean`	`supportsRowValueConstructorSyntax()`	Is this dialect known to support what ANSI-SQL terms "row value constructor" syntax; sometimes called tuple syntax.
`boolean`	`supportsSelectAliasInGroupByClause()`
`boolean`	`supportsSequences()`	Does this dialect support sequences?
`boolean`	`supportsUnboundedLobLocatorMaterialization()`	Is it supported to materialize a LOB locator outside the transaction in which it was created?
`boolean`	`supportsUnionAll()`	Does this dialect support UNION ALL, which is generally a faster variant of UNION?
`String`	`toBooleanValueString(boolean bool)`	The SQL literal value to which this database maps boolean values.
`boolean`	`useInputStreamToInsertBlob()`	Should LOBs (both BLOB and CLOB) be bound using stream operations (i.e.

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

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

- 构造器详细资料
  - PostgreSQL81Dialect
```
public PostgreSQL81Dialect()
```
    Constructs a PostgreSQL81Dialect
- 方法详细资料
  - getSqlTypeDescriptorOverride
```
public SqlTypeDescriptor getSqlTypeDescriptorOverride(int sqlCode)
```
    从类复制的说明: Dialect
    
    Returns the SqlTypeDescriptor that should be used to handle the given JDBC type code. Returns null if there is no override.
    
    覆盖:
    
    getSqlTypeDescriptorOverride 在类中 Dialect
    
    参数:
    
    sqlCode - A Types constant indicating the SQL column type
    
    返回:
    
    The SqlTypeDescriptor to use as an override, or null if there is no override.
  - getAddColumnString
```
public String getAddColumnString()
```
    从类复制的说明: Dialect
    
    The syntax used to add a column to a table (optional).
    
    覆盖:
    
    getAddColumnString 在类中 Dialect
    
    返回:
    
    The "add column" 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.
  - 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.
  - 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
  - getCascadeConstraintsString
```
public String getCascadeConstraintsString()
```
    从类复制的说明: Dialect
    
    Completely optional cascading drop clause
    
    覆盖:
    
    getCascadeConstraintsString 在类中 Dialect
    
    返回:
    
    String
  - 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.
  - supportsSequences
```
public boolean supportsSequences()
```
    从类复制的说明: Dialect
    
    Does this dialect support sequences?
    
    覆盖:
    
    supportsSequences 在类中 Dialect
    
    返回:
    
    True if sequences supported; false otherwise.
  - 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
  - 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
  - getForUpdateString
```
public String getForUpdateString(String aliases)
```
    从类复制的说明: Dialect
    
    Get the FOR UPDATE OF column_list fragment appropriate for this dialect given the aliases of the columns to be write locked.
    
    覆盖:
    
    getForUpdateString 在类中 Dialect
    
    参数:
    
    aliases - The columns to be write locked.
    
    返回:
    
    The appropriate FOR UPDATE OF column_list clause string.
  - getForUpdateString
```
public String getForUpdateString(String aliases,
                                 LockOptions lockOptions)
```
    从类复制的说明: Dialect
    
    Get the FOR UPDATE OF column_list fragment appropriate for this dialect given the aliases of the columns to be write locked.
    
    覆盖:
    
    getForUpdateString 在类中 Dialect
    
    参数:
    
    aliases - The columns to be write locked.
    
    lockOptions - the lock options to apply
    
    返回:
    
    The appropriate FOR UPDATE OF column_list clause string.
  - getNoColumnsInsertString
```
public String getNoColumnsInsertString()
```
    从类复制的说明: Dialect
    
    The fragment used to insert a row without specifying any column values. This is not possible on some databases.
    
    覆盖:
    
    getNoColumnsInsertString 在类中 Dialect
    
    返回:
    
    The appropriate empty values clause.
  - getCaseInsensitiveLike
```
public String getCaseInsensitiveLike()
```
    从类复制的说明: Dialect
    
    The name of the SQL function that can do case insensitive like comparison.
    
    覆盖:
    
    getCaseInsensitiveLike 在类中 Dialect
    
    返回:
    
    The dialect-specific "case insensitive" like function.
  - supportsCaseInsensitiveLike
```
public boolean supportsCaseInsensitiveLike()
```
    从类复制的说明: Dialect
    
    Does this dialect support case insensitive LIKE restrictions?
    
    覆盖:
    
    supportsCaseInsensitiveLike 在类中 Dialect
    
    返回:
    
    true if the underlying database supports case insensitive like comparison, false otherwise. The default is false.
  - getNativeIdentifierGeneratorStrategy
```
public String getNativeIdentifierGeneratorStrategy()
```
    从类复制的说明: Dialect
    
    Resolves the native generation strategy associated to this dialect.
    Comes into play whenever the user specifies the native generator.
    
    覆盖:
    
    getNativeIdentifierGeneratorStrategy 在类中 Dialect
    
    返回:
    
    The native generator strategy.
  - supportsOuterJoinForUpdate
```
public boolean supportsOuterJoinForUpdate()
```
    从类复制的说明: Dialect
    
    Does this dialect support FOR UPDATE in conjunction with outer joined rows?
    
    覆盖:
    
    supportsOuterJoinForUpdate 在类中 Dialect
    
    返回:
    
    True if outer joined rows can be locked via FOR UPDATE.
  - useInputStreamToInsertBlob
```
public boolean useInputStreamToInsertBlob()
```
    从类复制的说明: Dialect
    
    Should LOBs (both BLOB and CLOB) be bound using stream operations (i.e. PreparedStatement.setBinaryStream(int, java.io.InputStream, int)).
    
    覆盖:
    
    useInputStreamToInsertBlob 在类中 Dialect
    
    返回:
    
    True if BLOBs and CLOBs should be bound using stream operations.
  - 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.
  - getSelectClauseNullString
```
public String getSelectClauseNullString(int sqlType)
```
    Workaround for postgres bug #1453
    Given a Types type code, determine an appropriate null value to use in a select clause.
    One thing to consider here is that certain databases might require proper casting for the nulls here since the select here will be part of a UNION/UNION ALL.
    
    覆盖:
    
    getSelectClauseNullString 在类中 Dialect
    
    参数:
    
    sqlType - The Types type code.
    
    返回:
    
    The appropriate select clause value fragment.
  - supportsCommentOn
```
public boolean supportsCommentOn()
```
    从类复制的说明: Dialect
    
    Does this dialect/database support commenting on tables, columns, etc?
    
    覆盖:
    
    supportsCommentOn 在类中 Dialect
    
    返回:
    
    true if commenting is supported
  - 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.
  - requiresParensForTupleDistinctCounts
```
public boolean requiresParensForTupleDistinctCounts()
```
    从类复制的说明: Dialect
    
    If Dialect.supportsTupleDistinctCounts() is true, does the Dialect require the tuple to be wrapped with parens?
    
    覆盖:
    
    requiresParensForTupleDistinctCounts 在类中 Dialect
    
    返回:
    
    boolean
  - toBooleanValueString
```
public String toBooleanValueString(boolean bool)
```
    从类复制的说明: Dialect
    
    The SQL literal value to which this database maps boolean values.
    
    覆盖:
    
    toBooleanValueString 在类中 Dialect
    
    参数:
    
    bool - The boolean value
    
    返回:
    
    The appropriate SQL literal.
  - 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
  - registerResultSetOutParameter
```
public int registerResultSetOutParameter(CallableStatement statement,
                                         int col)
                                  throws SQLException
```
    从类复制的说明: Dialect
    
    Registers a parameter (either OUT, or the new REF_CURSOR param type available in Java 8) capable of returning ResultSet *by position*. Pre-Java 8, registering such ResultSet-returning parameters varied greatly across database and drivers; hence its inclusion as part of the Dialect contract.
    
    覆盖:
    
    registerResultSetOutParameter 在类中 Dialect
    
    参数:
    
    statement - The callable statement.
    
    col - The bind position at which to register the output param.
    
    返回:
    
    The number of (contiguous) bind positions used.
    
    抛出:
    
    SQLException - Indicates problems registering the param.
  - getResultSet
```
public ResultSet getResultSet(CallableStatement ps)
                       throws SQLException
```
    从类复制的说明: Dialect
    
    Given a callable statement previously processed by Dialect.registerResultSetOutParameter(java.sql.CallableStatement, int), extract the ResultSet from the OUT parameter.
    
    覆盖:
    
    getResultSet 在类中 Dialect
    
    参数:
    
    ps - The callable statement.
    
    返回:
    
    The extracted result set.
    
    抛出:
    
    SQLException - Indicates problems extracting the result set.
  - 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
```
protected String getCreateSequenceString(String sequenceName,
                                         int initialValue,
                                         int incrementSize)
```
    only necessary for postgre < 7.4 See http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/create_sequence.sgml
    Overloaded form of Dialect.getCreateSequenceString(String), additionally taking the initial value and increment size to be applied to the sequence definition.
    The default definition is to suffix Dialect.getCreateSequenceString(String) with the string: " start with {initialValue} increment by {incrementSize}" where {initialValue} and {incrementSize} are replacement placeholders. Generally dialects should only need to override this method if different key phrases are used to apply the allocation information.
    
    覆盖:
    
    getCreateSequenceString 在类中 Dialect
    
    参数:
    
    sequenceName - The name of the sequence
    
    initialValue - The initial value to apply to 'create sequence' statement
    
    incrementSize - The increment value to apply to 'create sequence' statement
    
    返回:
    
    The sequence creation command
  - supportsEmptyInList
```
public boolean supportsEmptyInList()
```
    从类复制的说明: Dialect
    
    Does this dialect support empty IN lists?
    For example, is [where XYZ in ()] a supported construct?
    
    覆盖:
    
    supportsEmptyInList 在类中 Dialect
    
    返回:
    
    True if empty in lists are supported; false otherwise.
  - supportsExpectedLobUsagePattern
```
public boolean supportsExpectedLobUsagePattern()
```
    从类复制的说明: Dialect
    
    Expected LOB usage pattern is such that I can perform an insert via prepared statement with a parameter binding for a LOB value without crazy casting to JDBC driver implementation-specific classes...
    Part of the trickiness here is the fact that this is largely driver dependent. For example, Oracle (which is notoriously bad with LOB support in their drivers historically) actually does a pretty good job with LOB support as of the 10.2.x versions of their drivers...
    
    覆盖:
    
    supportsExpectedLobUsagePattern 在类中 Dialect
    
    返回:
    
    True if normal LOB usage patterns can be used with this driver; false if driver-specific hookiness needs to be applied.
  - 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.
  - supportsUnboundedLobLocatorMaterialization
```
public boolean supportsUnboundedLobLocatorMaterialization()
```
    从类复制的说明: Dialect
    
    Is it supported to materialize a LOB locator outside the transaction in which it was created?
    Again, part of the trickiness here is the fact that this is largely driver dependent.
    NOTE: all database I have tested which Dialect.supportsExpectedLobUsagePattern() also support the ability to materialize a LOB outside the owning transaction...
    
    覆盖:
    
    supportsUnboundedLobLocatorMaterialization 在类中 Dialect
    
    返回:
    
    True if unbounded materialization is supported; false otherwise.
  - 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.
  - getWriteLockString
```
public String getWriteLockString(int timeout)
```
    从类复制的说明: Dialect
    
    Get the string to append to SELECT statements to acquire WRITE locks for this dialect. Location of the returned string is treated the same as getForUpdateString.
    
    覆盖:
    
    getWriteLockString 在类中 Dialect
    
    参数:
    
    timeout - in milliseconds, -1 for indefinite wait and 0 for no wait.
    
    返回:
    
    The appropriate LOCK clause string.
  - getWriteLockString
```
public String getWriteLockString(String aliases,
                                 int timeout)
```
    从类复制的说明: Dialect
    
    Get the string to append to SELECT statements to acquire WRITE locks for this dialect given the aliases of the columns to be write locked. Location of the of the returned string is treated the same as getForUpdateString.
    
    覆盖:
    
    getWriteLockString 在类中 Dialect
    
    参数:
    
    aliases - The columns to be read locked.
    
    timeout - in milliseconds, -1 for indefinite wait and 0 for no wait.
    
    返回:
    
    The appropriate LOCK clause string.
  - getReadLockString
```
public String getReadLockString(int timeout)
```
    从类复制的说明: Dialect
    
    Get the string to append to SELECT statements to acquire READ locks for this dialect. Location of the returned string is treated the same as getForUpdateString.
    
    覆盖:
    
    getReadLockString 在类中 Dialect
    
    参数:
    
    timeout - in milliseconds, -1 for indefinite wait and 0 for no wait.
    
    返回:
    
    The appropriate LOCK clause string.
  - getReadLockString
```
public String getReadLockString(String aliases,
                                int timeout)
```
    从类复制的说明: Dialect
    
    Get the string to append to SELECT statements to acquire READ locks for this dialect given the aliases of the columns to be read locked. Location of the returned string is treated the same as getForUpdateString.
    
    覆盖:
    
    getReadLockString 在类中 Dialect
    
    参数:
    
    aliases - The columns to be read locked.
    
    timeout - in milliseconds, -1 for indefinite wait and 0 for no wait.
    
    返回:
    
    The appropriate LOCK clause string.
  - supportsRowValueConstructorSyntax
```
public boolean supportsRowValueConstructorSyntax()
```
    从类复制的说明: Dialect
    
    Is this dialect known to support what ANSI-SQL terms "row value constructor" syntax; sometimes called tuple syntax.
    Basically, does it support syntax like "... where (FIRST_NAME, LAST_NAME) = ('Steve', 'Ebersole') ...".
    
    覆盖:
    
    supportsRowValueConstructorSyntax 在类中 Dialect
    
    返回:
    
    True if this SQL dialect is known to support "row value constructor" syntax; false otherwise.
  - getForUpdateNowaitString
```
public String getForUpdateNowaitString()
```
    从类复制的说明: Dialect
    
    Retrieves the FOR UPDATE NOWAIT syntax specific to this dialect.
    
    覆盖:
    
    getForUpdateNowaitString 在类中 Dialect
    
    返回:
    
    The appropriate FOR UPDATE NOWAIT clause string.
  - getForUpdateNowaitString
```
public String getForUpdateNowaitString(String aliases)
```
    从类复制的说明: Dialect
    
    Get the FOR UPDATE OF column_list NOWAIT fragment appropriate for this dialect given the aliases of the columns to be write locked.
    
    覆盖:
    
    getForUpdateNowaitString 在类中 Dialect
    
    参数:
    
    aliases - The columns to be write locked.
    
    返回:
    
    The appropriate FOR UPDATE OF colunm_list NOWAIT clause string.
  - getCallableStatementSupport
```
public CallableStatementSupport getCallableStatementSupport()
```
    覆盖:
    
    getCallableStatementSupport 在类中 Dialect
  - getResultSet
```
public ResultSet getResultSet(CallableStatement statement,
                              int position)
                       throws SQLException
```
    从类复制的说明: Dialect
    
    Given a callable statement previously processed by Dialect.registerResultSetOutParameter(java.sql.CallableStatement, int), extract the ResultSet.
    
    覆盖:
    
    getResultSet 在类中 Dialect
    
    参数:
    
    statement - The callable statement.
    
    position - The bind position at which to register the output param.
    
    返回:
    
    The extracted result set.
    
    抛出:
    
    SQLException - Indicates problems extracting the result set.
  - getResultSet
```
public ResultSet getResultSet(CallableStatement statement,
                              String name)
                       throws SQLException
```
    从类复制的说明: Dialect
    
    Given a callable statement previously processed by Dialect.registerResultSetOutParameter(java.sql.CallableStatement, int), extract the ResultSet from the OUT parameter.
    
    覆盖:
    
    getResultSet 在类中 Dialect
    
    参数:
    
    statement - The callable statement.
    
    name - The parameter name (for drivers which support named parameters).
    
    返回:
    
    The extracted result set.
    
    抛出:
    
    SQLException - Indicates problems extracting the result set.
  - qualifyIndexName
```
public boolean qualifyIndexName()
```
    从类复制的说明: Dialect
    
    Do we need to qualify index names with the schema name?
    
    覆盖:
    
    qualifyIndexName 在类中 Dialect
    
    返回:
    
    boolean
  - getIdentityColumnSupport
```
public IdentityColumnSupport getIdentityColumnSupport()
```
    从类复制的说明: Dialect
    
    Get the appropriate IdentityColumnSupport
    
    覆盖:
    
    getIdentityColumnSupport 在类中 Dialect
    
    返回:
    
    the IdentityColumnSupport
  - supportsNationalizedTypes
```
public boolean supportsNationalizedTypes()
```
    从类复制的说明: Dialect
    
    Does this dialect supports Nationalized Types
    
    覆盖:
    
    supportsNationalizedTypes 在类中 Dialect
    
    返回:
    
    boolean
  - supportsNoWait
```
public boolean supportsNoWait()
```
    从类复制的说明: Dialect
    
    Does this dialect/database support NO_WAIT timeout.
    
    覆盖:
    
    supportsNoWait 在类中 Dialect
    
    返回:
    
    true if NO_WAIT is supported
  - supportsJdbcConnectionLobCreation
```
public boolean supportsJdbcConnectionLobCreation(DatabaseMetaData databaseMetaData)
```
    从类复制的说明: Dialect
    
    Check whether the JDBC Connection supports creating LOBs via Connection.createBlob(), Connection.createNClob() or Connection.createClob().
    
    覆盖:
    
    supportsJdbcConnectionLobCreation 在类中 Dialect
    
    参数:
    
    databaseMetaData - JDBC DatabaseMetaData which can be used if LOB creation is supported only starting from a given Driver version
    
    返回:
    
    true if LOBs can be created via the JDBC Connection.
  - supportsSelectAliasInGroupByClause
```
public boolean supportsSelectAliasInGroupByClause()
```
    覆盖:
    
    supportsSelectAliasInGroupByClause 在类中 Dialect

类 PostgreSQL81Dialect

字段概要

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

构造器概要

方法概要

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

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

构造器详细资料

PostgreSQL81Dialect

方法详细资料

getSqlTypeDescriptorOverride

getAddColumnString

getSequenceNextValString

getSelectSequenceNextValString

getCreateSequenceString

getDropSequenceString

getCascadeConstraintsString

dropConstraints

supportsSequences

getQuerySequencesString

getLimitHandler

supportsLimit

getLimitString

bindLimitParametersInReverseOrder

getForUpdateString

getForUpdateString

getNoColumnsInsertString

getCaseInsensitiveLike

supportsCaseInsensitiveLike

getNativeIdentifierGeneratorStrategy

supportsOuterJoinForUpdate

useInputStreamToInsertBlob

supportsUnionAll

getSelectClauseNullString

supportsCommentOn

getDefaultMultiTableBulkIdStrategy

supportsCurrentTimestampSelection

isCurrentTimestampSelectStringCallable

getCurrentTimestampSelectString

requiresParensForTupleDistinctCounts

toBooleanValueString

getViolatedConstraintNameExtracter

buildSQLExceptionConversionDelegate

registerResultSetOutParameter

getResultSet

supportsPooledSequences

getCreateSequenceString

supportsEmptyInList

supportsExpectedLobUsagePattern

supportsLobValueChangePropogation

supportsUnboundedLobLocatorMaterialization

getForUpdateString

getWriteLockString

getWriteLockString

getReadLockString

getReadLockString

supportsRowValueConstructorSyntax

getForUpdateNowaitString

getForUpdateNowaitString

getCallableStatementSupport

getResultSet

getResultSet

qualifyIndexName

getIdentityColumnSupport

supportsNationalizedTypes

supportsNoWait

supportsJdbcConnectionLobCreation

supportsSelectAliasInGroupByClause