This is false only by default. The database can be configured to be case-insensitive.

Completely optional cascading drop clause

Slight variation on CreateTableString. The command used to create a multiset table.

Command used to create a table.

Get any fragments needing to be postfixed to the command for temporary table creation.

Command used to create a temporary table.

Retrieve a set of default Hibernate properties for this database.

Only needed if the Dialect does not have SupportsForeignKeyConstraintInAlterTable.

Do we need to drop constraints before dropping tables in the dialect?

Only needed if the Dialect does not have SupportsForeignKeyConstraintInAlterTable.

Retrieves the FOR UPDATE NOWAIT syntax specific to this dialect

Is FOR UPDATE OF syntax supported?

Aggregate SQL functions as defined in general. This is a case-insensitive hashtable!

Set this to false if no table-level primary key constraint should be generated when an identity column has been specified for the table. This is used as a work-around for SQLite so it doesn't tell us we have "more than one primary key".

Whether this dialect has an identity clause added to the data type or a completely separate identity data type.

The keyword used to insert a generated value into an identity column (or null). Need if the dialect does not support inserts that specify no column values.

The class (which implements IIdentifierGenerator) which acts as this dialects identity-style generation strategy.

The name of the SQL function that transforms a string to lowercase

The class (which implements IIdentifierGenerator) which acts as this dialects native generation strategy.

The keyword used to insert a row without specifying any column values

For limit clauses, indicates whether to use 0 or 1 as the offset that returns the first row. Should be true if the first row is at offset 1.

The keyword used to create a primary key constraint

Get the select command used retrieve the names of all sequences.

Does this dialect support using a JDBC bind parameter as an argument to a function or procedure call?

Does this dialect support definition of cascade delete constraints which can cause circular chains?

Does this dialect support column-level check constraints?

Does this dialect support adding foreign key constraints via alter table? If not, it's assumed they can only be added through create table.

Does the dialect support the syntax 'drop table NAME if exists'

Does the dialect support the syntax 'drop table if exists NAME'

Does this Dialect have some kind of LIMIT syntax?

Does this Dialect support an offset?

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: {@link java.sql.Blob#setBinaryStream}, {@link java.sql.Blob#setBytes(long, byte[])}, {@link java.sql.Blob#setBytes(long, byte[], int, int)}, or {@link java.sql.Blob#truncate(long)}.

For CLOBs, the internal value might be changed by: {@link java.sql.Clob#setAsciiStream(long)}, {@link java.sql.Clob#setCharacterStream(long)}, {@link java.sql.Clob#setString(long, String)}, {@link java.sql.Clob#setString(long, String, int, int)}, or {@link java.sql.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 {@link #supportsExpectedLobUsagePattern}.

Does this dialect support FOR UPDATE in conjunction with outer joined rows?

Does this dialect support parameters within the select clause of INSERT ... SELECT ... statements?

Does this dialect support "pooled" sequences. Not aware of a better name for this. Essentially can we specify the initial and increment values?

Does this dialect support asking the result set its positioning information on forward only cursors. Specifically, in the case of scrolling fetches, Hibernate needs to use {@link java.sql.ResultSet#isAfterLast} and {@link java.sql.ResultSet#isBeforeFirst}. Certain drivers do not allow access to these methods for forward only cursors.

NOTE : this is highly driver dependent!

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') ...".

If the dialect supports {@link #supportsRowValueConstructorSyntax() row values}, does it offer such support in IN lists as well?

For example, "... where (FIRST_NAME, LAST_NAME) IN ( (?, ?), (?, ?) ) ..."

Does this dialect support sequences?

Supports splitting batches using GO T-SQL command

Does this dialect support referencing the table being mutated in a subquery. The "table being mutated" is the table referenced in an UPDATE or a DELETE query. And so can that table then be referenced in a subquery of said UPDATE/DELETE query.

For example, would the following two syntaxes be supported:

• delete from TABLE_A where ID not in ( select ID from TABLE_A )
• update TABLE_A set NON_ID = 'something' where ID in ( select ID from TABLE_A)

Are subselects supported as the left-hand-side (LHS) of IN-predicates.

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

Does this dialect support subselects?

Does this dialect support table-level check constraints?

Sybase ASE 15 temporary tables are not supported

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 {@link #supportsExpectedLobUsagePattern()} also support the ability to materialize a LOB outside the owning transaction...

Does this dialect support the UNIQUE column syntax?

Does this dialect support adding Unique constraints via create and alter table ?

Can parameters be used for a statement containing a LIMIT?

Gives the best resolution that the database can use for storing date/time values, in ticks.

Should LOBs (both BLOB and CLOB) be bound using stream operations (i.e. {@link java.sql.PreparedStatement#setBinaryStream}).

Does the LIMIT clause take a "maximum" row number instead of a total number of returned rows?