类 IngresDialect

  • 所有已实现的接口:
    ConversionContext
    直接已知子类:
    Ingres9Dialect

    public class IngresDialect
    extends Dialect
    An SQL dialect for Ingres 9.2.

    Known limitations:

    • Only supports simple constants or columns on the left side of an IN, making (1,2,3) in (...) or (subselect) in (...) non-supported.
    • Supports only 39 digits in decimal.
    • Explicitly set USE_GET_GENERATED_KEYS property to false.
    • Perform string casts to varchar; removes space padding.
    作者:
    Ian Booth, Bruce Lunsford, Max Rydahl Andersen, Raymond Fan
    • 构造器详细资料

      • IngresDialect

        public IngresDialect()
        Constructs a IngresDialect
    • 方法详细资料

      • getSelectGUIDString

        public String getSelectGUIDString()
        从类复制的说明: Dialect
        Get the command used to select a GUID from the underlying database.

        Optional operation.

        覆盖:
        getSelectGUIDString 在类中 Dialect
        返回:
        The appropriate command.
      • 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.
      • getAddColumnString

        public String getAddColumnString()
        从类复制的说明: Dialect
        The syntax used to add a column to a table (optional).
        覆盖:
        getAddColumnString 在类中 Dialect
        返回:
        The "add column" fragment.
      • getNullColumnString

        public String getNullColumnString()
        从类复制的说明: Dialect
        The keyword used to specify a nullable column.
        覆盖:
        getNullColumnString 在类中 Dialect
        返回:
        String
      • supportsSequences

        public boolean supportsSequences()
        从类复制的说明: Dialect
        Does this dialect support sequences?
        覆盖:
        supportsSequences 在类中 Dialect
        返回:
        True if sequences supported; false otherwise.
      • 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.
      • 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
      • getLowercaseFunction

        public String getLowercaseFunction()
        从类复制的说明: Dialect
        The name of the SQL function that transforms a string to lowercase
        覆盖:
        getLowercaseFunction 在类中 Dialect
        返回:
        The dialect-specific lowercase function.
      • getLimitHandler

        public LimitHandler getLimitHandler()
        从类复制的说明: Dialect
        Returns the delegate managing LIMIT clause.
        覆盖:
        getLimitHandler 在类中 Dialect
        返回:
        LIMIT clause delegate.
      • getDefaultLimitHandler

        protected LimitHandler getDefaultLimitHandler()
      • 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.
      • supportsLimitOffset

        public boolean supportsLimitOffset()
        从类复制的说明: Dialect
        Does this dialect's LIMIT support (if any) additionally support specifying an offset?
        覆盖:
        supportsLimitOffset 在类中 Dialect
        返回:
        True if the dialect supports an offset within the limit support.
      • getLimitString

        public String getLimitString​(String querySelect,
                                     int offset,
                                     int limit)
        从类复制的说明: Dialect
        Given a limit and an offset, apply the limit clause to the query.
        覆盖:
        getLimitString 在类中 Dialect
        参数:
        querySelect - The query to which to apply the limit.
        offset - The offset of the limit
        limit - The limit of the limit ;)
        返回:
        The modified query statement with the limit applied.
      • supportsVariableLimit

        public boolean supportsVariableLimit()
        从类复制的说明: Dialect
        Does this dialect support bind variables (i.e., prepared statement parameters) for its limit/offset?
        覆盖:
        supportsVariableLimit 在类中 Dialect
        返回:
        True if bind variables can be used; false otherwise.
      • useMaxForLimit

        public boolean useMaxForLimit()
        从类复制的说明: Dialect
        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?

        覆盖:
        useMaxForLimit 在类中 Dialect
        返回:
        True if limit is relative from offset; false otherwise.
      • getCurrentTimestampSQLFunctionName

        public String getCurrentTimestampSQLFunctionName()
        从类复制的说明: Dialect
        The name of the database-specific SQL function for retrieving the current timestamp.
        覆盖:
        getCurrentTimestampSQLFunctionName 在类中 Dialect
        返回:
        The function name.
      • supportsSubselectAsInPredicateLHS

        public boolean supportsSubselectAsInPredicateLHS()
        从类复制的说明: Dialect
        Are subselects supported as the left-hand-side (LHS) of IN-predicates.

        In other words, is syntax like "... IN (1, 2, 3) ..." supported?

        覆盖:
        supportsSubselectAsInPredicateLHS 在类中 Dialect
        返回:
        True if subselects can appear as the LHS of an in-predicate; false otherwise.
      • 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.
      • supportsTupleDistinctCounts

        public boolean supportsTupleDistinctCounts()
        从类复制的说明: Dialect
        Does this dialect support `count(distinct a,b)`?
        覆盖:
        supportsTupleDistinctCounts 在类中 Dialect
        返回:
        True if the database supports counting distinct tuples; false otherwise.