Initializes a new instance of the MySQLDialect class

Provided we SupportsInsertSelectIdentity, then attch the "select identity" clause to the insert statement.

Some dialects support an alternative means to SELECT FOR UPDATE, whereby a "lock hint" is appends to the table name in the from clause.

Modifies the given SQL by applying the appropriate updates for the specified lock modes and key columns.

Build an instance of the ISQLExceptionConverter preferred by this dialect for converting DbException into NHibernate's ADOException hierarchy.

Create a CaseFragment strategy responsible for handling this dialect's variations in how CASE statements are handled.

Create a JoinFragment strategy responsible for handling this dialect's variations in how joins are handled.

Do we need to drop the temporary table after use?

Determines whether the specified Object is equal to the current Object.

Allows an object to try to free resources and perform other cleanup operations before it is reclaimed by garbage collection.

Generate a temporary table name given the bas table.

The syntax used to add a primary key constraint to a table

Get the name of the database type appropriate for casting operations (via the CAST() SQL function) for the given SqlType typecode.

Typically dialects which support sequences can create a sequence with a single command.

Overloaded form of GetCreateSequenceString(String), additionally taking the initial value and increment size to be applied to the sequence definition.

An optional multi-line form for databases which SupportsPooledSequences.

Create the SQL string to drop a foreign key constraint.

Create the SQL string to drop an index.

Create the SQL string to drop a primary key constraint.

Typically dialects which support sequences can drop a sequence with a single command.

The multiline script used to drop a sequence.

Return SQL needed to drop the named table. May (and should) use some form of "if exists" clause, and cascade constraints.

Get the FOR UPDATE OF column_list NOWAIT fragment appropriate for this dialect given the aliases of the columns to be write locked.

Get the FOR UPDATE OF column_list fragment appropriate for this dialect given the aliases of the columns to be write locked.

Given a lock mode, determine the appropriate for update fragment to use.

Serves as a hash function for a particular type.

Get the name of the Hibernate IType associated with th given DbType typecode.

Get the name of the Hibernate IType associated with the given DbType typecode with the given storage specification parameters.

The syntax used during DDL to define a column as being an IDENTITY of a particular type.

Get the select command to use to retrieve the last generated IDENTITY value for a particular table

The syntax that is used to check if a constraint exists before dropping it

The syntax that is used to close the if for a constraint exists check, used for dialects that requires begin/end for ifs

The syntax that is used to check if a constraint does not exists before creating it

The syntax that is used to close the if for a constraint exists check, used for dialects that requires begin/end for ifs

Generates a string to limit the result set to a number of maximum results with a specified offset into the results. Expects any database-specific offset and limit adjustments to have already been performed (ex. UseMaxForLimit, OffsetStartsAtOne). Performs error checking based on the various dialect limit support options. If both parameters and fixed valeus are specified, this will use the parameter option if possible. Otherwise, it will fall back to a fixed string.

Some databases require that a limit statement contain the maximum row number instead of the number of rows to retrieve. This method adjusts source limit and offset values to account for this.

Get a strategy instance which knows how to acquire a database-level lock of the specified mode for this dialect.

Gets the name of the longest registered type for a particular DbType.

Some databases use limit row offsets that start at one instead of zero. This method adjusts a desired offset using the OffsetStartsAtOne flag.

Given a callable statement previously processed by RegisterResultSetOutParameter(DbCommand, Int32), extract the DbDataReader from the OUT parameter.

Given a DbType type code, determine an appropriate null value to use in a select clause.

Generate the select expression fragment that will retrieve the next value of a sequence as part of another (typically DML) statement.

Generate the appropriate select statement to to retreive the next value of a sequence.

Gets the Type of the current instance.

Get the name of the database type associated with the given SqlType,

Get the name of the database type associated with the given SqlType.

Checks to see if the name has been quoted.

Creates a shallow copy of the current Object.

Does the dialect require that temporary table DDL statements occur in isolation from other statements? This would be the case if the creation would cause any current transaction to get committed implicitly.

Quotes a name.

Quotes a name for being used as a aliasname

Quotes a name for being used as a columnname

Quotes a name for being used as a schemaname

Quotes a name for being used as a tablename

Suclasses register a typename for the given type code, to be used in CAST() statements.

Suclasses register a typename for the given type code. $l in the typename will be replaced by the column length (if appropriate).

Subclasses register a typename for the given type code and maximum column length. $l in the type name will be replaced by the column length (if appropriate)

(Inherited from Dialect.)

Registers a Hibernate IType name for the given DbType type code.

Registers a Hibernate IType name for the given DbType type code and maximum column length.

Registers an OUT parameter which will be returing a DbDataReader. How this is accomplished varies greatly from DB to DB, hence its inclusion (along with {@link #getResultSet}) here.

The SQL literal value to which this database maps boolean values.

Returns a string that represents the current object.

Unquotes and unescapes an already quoted name

Unquotes an array of Quoted Names.

Apply a "between" constraint to the named property Note: throws an exception outside of a QueryOver expression

Apply an "in" constraint to the named property Note: throws an exception outside of a QueryOver expression

Apply an "in" constraint to the named property Note: throws an exception outside of a QueryOver expression

(Overrides Dialect..::..AddColumnString.)

Are string comparisons implicitly case insensitive. In other words, does [where 'XYZ' = 'xyz'] resolve to true?

Completely optional cascading drop clause

(Overrides Dialect..::..CloseQuote.)

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.

Retrieve the command used to retrieve the current timestammp from the database.

The name of the database-specific SQL function for retrieving the current timestamp.

Retrieve a set of default Hibernate properties for this database.

Only needed if the Dialect does not have SupportsForeignKeyConstraintInAlterTable.

For the underlying database, is READ_COMMITTED isolation implemented by forcing readers to wait for write locks to be released?

For the underlying database, is REPEATABLE_READ isolation implemented by forcing writers to wait for read locks to be released?

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?

Get the string to append to SELECT statements to acquire locks for this dialect.

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.

(Overrides Dialect..::..IdentityColumnString.)

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.

(Overrides Dialect..::..IdentitySelectString.)

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

Should the value returned by CurrentTimestampSelectString be treated as callable. Typically this indicates that JDBC escape sytnax is being used...

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

The keyword used to specify a nullable column

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.

(Overrides Dialect..::..OpenQuote.)

The keyword used to create a primary key constraint

(Overrides Dialect..::..QualifyIndexName.)

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

Get the command used to select a GUID from the underlying database. (Optional operation.)

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 a way to retrieve the database's current timestamp value?

Does this dialect support empty IN lists? For example, is [where XYZ in ()] a supported construct?

Does the dialect support an exists statement in the select clause?

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...

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

(Overrides Dialect..::..SupportsIdentityColumns.)

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

Does the dialect support some form of inserting and selecting the generated IDENTITY value all in the same statement.

(Overrides Dialect..::..SupportsLimit.)

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 table-level check constraints?

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 UNION ALL, which is generally a faster variant of UNION? True if UNION ALL is supported; false otherwise.

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?