Interface SqlConformance

All Known Implementing Classes:
SqlAbstractConformance, SqlConformanceEnum, SqlDelegatingConformance

public interface SqlConformance
Enumeration of valid SQL compatibility modes.

For most purposes, one of the built-in compatibility modes in enum SqlConformanceEnum will suffice.

If you wish to implement this interface to build your own conformance, we strongly recommend that you extend SqlAbstractConformance, or use a SqlDelegatingConformance, so that you won't be broken by future changes.

See Also:
  • Field Summary

    Fields
    Modifier and Type
    Field
    Description
    static final SqlConformanceEnum
    Deprecated.
    static final SqlConformanceEnum
    Deprecated.
    static final SqlConformanceEnum
    Deprecated.
    static final SqlConformanceEnum
    Deprecated.
    static final SqlConformanceEnum
    Deprecated.
    static final SqlConformanceEnum
    Deprecated.
    static final SqlConformanceEnum
    Deprecated.
  • Method Summary

    Modifier and Type
    Method
    Description
    boolean
    Whether directly alias array items in UNNEST.
    boolean
    Whether this dialect allows character literals as column aliases.
    boolean
    Whether to allow SQL syntax "ROW(expr1, expr2, expr3)".
    boolean
    Whether to allow mixing table columns with extended columns in INSERT (or UPSERT).
    boolean
    Whether TRIM should support more than one trim character.
    boolean
    Whether to allow geo-spatial extensions, including the GEOMETRY type.
    boolean
    Whether to allow hyphens in an unquoted table name.
    boolean
    Whether to allow parentheses to be specified in calls to niladic functions and procedures (that is, functions and procedures with no parameters).
    boolean
    Whether interval literals should allow plural time units such as "YEARS" and "DAYS" in interval literals.
    boolean
    Whether to allow a qualified common column in a query that has a NATURAL join or a join with a USING clause.
    boolean
    Whether CROSS APPLY and OUTER APPLY operators are allowed in the parser.
    boolean
    Whether the bang-equal token != is allowed as an alternative to <> in the parser.
    boolean
    Whether FROM clause is required in a SELECT statement.
    boolean
    Whether to allow aliases from the SELECT clause to be used as column names in the GROUP BY clause.
    boolean
    Whether GROUP BY 2 is interpreted to mean 'group by the 2nd column in the select list'.
    boolean
    Whether to allow aliases from the SELECT clause to be used as column names in the HAVING clause.
    boolean
    Whether to allow INSERT (or UPSERT) with no column list but fewer values than the target table.
    boolean
    Whether this dialect supports features from a wide variety of dialects.
    boolean
    Whether to allow the SQL syntax "LIMIT start, count".
    boolean
    Whether MINUS is allowed as an alternative to EXCEPT in the parser.
    boolean
    Whether to allow the SQL syntax "OFFSET start LIMIT count" (that is, OFFSET before LIMIT, in addition to LIMIT before OFFSET and OFFSET before FETCH).
    boolean
    Whether the "%" operator is allowed by the parser as an alternative to the mod function.
    boolean
    Whether 'ORDER BY x' is interpreted to mean 'sort by the select list item whose alias is x' even if there is a column called x.
    boolean
    Whether "empno" is invalid in "select empno as x from emp order by empno" because the alias "x" obscures it.
    boolean
    Whether 'ORDER BY 2' is interpreted to mean 'sort by the 2nd column in the select list'.
    Controls the behavior of operators that are part of Standard SQL but nevertheless have different behavior in different databases.
    boolean
    Whether the least restrictive type of a number of CHAR types of different lengths should be a VARCHAR type.
    boolean
    Whether to split a quoted table name.