java.lang.Object | ||
↳ | org.hibernate.dialect.Dialect | |
↳ | org.hibernate.dialect.SQLServerDialect |
Known Direct Subclasses |
A dialect for Microsoft SQL Server 2000
[Expand]
Inherited Constants | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
From class
org.hibernate.dialect.Dialect
|
Public Constructors | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Public Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Use insert table(...) values(...) select SCOPE_IDENTITY()
| |||||||||||
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.
| |||||||||||
Are string comparisons implicitly case insensitive.
| |||||||||||
The character specific to this dialect used to close a quoted identifier.
| |||||||||||
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 the temporary table after use?
| |||||||||||
Generate a temporary table name given the base table.
| |||||||||||
The syntax used to add a column to a table (optional).
| |||||||||||
Retrieve the command used to retrieve the current timestamp from the
database.
| |||||||||||
Get the string to append to SELECT statements to acquire locks
for this dialect.
| |||||||||||
The syntax used during DDL to define a column as being an IDENTITY.
| |||||||||||
Get the select command to use to retrieve the last generated IDENTITY
value.
| |||||||||||
Given a limit and an offset, apply the limit clause to the query.
| |||||||||||
The fragment used to insert a row without specifying any column values.
| |||||||||||
The keyword used to specify a nullable column.
| |||||||||||
Given a callable statement previously processed by
registerResultSetOutParameter(CallableStatement, int) ,
extract the ResultSet from the OUT parameter. | |||||||||||
Get the command used to select a GUID from the underlying database.
| |||||||||||
Should the value returned by
getCurrentTimestampSelectString()
be treated as callable. | |||||||||||
The character specific to this dialect used to begin a quoted identifier.
| |||||||||||
Do we need to qualify index names with the schema name?
| |||||||||||
Registers an OUT parameter which will be returning a
ResultSet . | |||||||||||
Does this dialect support definition of cascade delete constraints
which can cause circular chains?
| |||||||||||
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?
| |||||||||||
Does this dialect support identity column key generation?
| |||||||||||
Does the dialect support some form of inserting and selecting
the generated IDENTITY value all in the same statement.
| |||||||||||
Does this dialect support some form of limiting query results
via a SQL clause?
| |||||||||||
Does this dialect's LIMIT support (if any) additionally
support specifying 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...
| |||||||||||
Does this dialect support asking the result set its positioning
information on forward only cursors.
| |||||||||||
Does this dialect support temporary tables?
| |||||||||||
Does this dialect support `count(distinct a,b)`?
| |||||||||||
Does this dialect support UNION ALL, which is generally a faster
variant of UNION?
| |||||||||||
Does this dialect support bind variables (i.e., prepared statement
parameters) for its limit/offset?
| |||||||||||
Does the LIMIT clause take a "maximum" row number instead
of a total number of returned rows?
This is easiest understood via an example.
|
[Expand]
Inherited Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
From class
org.hibernate.dialect.Dialect
| |||||||||||
From class
java.lang.Object
|
Use insert table(...) values(...) select SCOPE_IDENTITY()
insertSQL | The insert command |
---|
Some dialects support an alternative means to SELECT FOR UPDATE, whereby a "lock hint" is appends to the table name in the from clause.
contributed by Helge Schulzmode | The lock mode to apply |
---|---|
tableName | The name of the table to which to apply the lock hint. |
Modifies the given SQL by applying the appropriate updates for the specified lock modes and key columns.
The behavior here is that of an ANSI SQL SELECT FOR UPDATE. This method is really intended to allow dialects which do not support SELECT FOR UPDATE to achieve this in their own fashion.sql | the SQL string to modify |
---|---|
aliasedLockOptions | lock options indexed by aliased table names. |
keyColumnNames | a map of key columns indexed by aliased table names. |
Are string comparisons implicitly case insensitive.
In other words, does [where 'XYZ' = 'xyz'] resolve to true?The character specific to this dialect used to close a quoted identifier.
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 the temporary table after use?
Generate a temporary table name given the base table.
baseTableName | The table name from which to base the temp table name. |
---|
The syntax used to add a column to a table (optional).
Retrieve the command used to retrieve the current timestamp from the database.
Get the string to append to SELECT statements to acquire locks for this dialect.
The syntax used during DDL to define a column as being an IDENTITY.
Get the select command to use to retrieve the last generated IDENTITY value.
Given a limit and an offset, apply the limit clause to the query.
querySelect | The query to which to apply the limit. |
---|---|
offset | The offset of the limit |
limit | The limit of the limit ;) |
The fragment used to insert a row without specifying any column values. This is not possible on some databases.
Given a callable statement previously processed by registerResultSetOutParameter(CallableStatement, int)
,
extract the ResultSet
from the OUT parameter.
ps | The callable statement. |
---|
SQLException |
---|
Get the command used to select a GUID from the underlying database.
Optional operation.Should the value returned by getCurrentTimestampSelectString()
be treated as callable. Typically this indicates that JDBC escape
syntax is being used...
getCurrentTimestampSelectString()
return
is callable; false otherwise.
The character specific to this dialect used to begin a quoted identifier.
Do we need to qualify index names with the schema name?
Registers an OUT parameter which will be returning a
ResultSet
. How this is accomplished varies greatly
from DB to DB, hence its inclusion (along with getResultSet(CallableStatement)
) here.
statement | The callable statement. |
---|---|
col | The bind position at which to register the OUT param. |
SQLException |
---|
Does this dialect support definition of cascade delete constraints which can cause circular chains?
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?
Does this dialect support identity column key generation?
Does the dialect support some form of inserting and selecting the generated IDENTITY value all in the same statement.
Does this dialect support some form of limiting query results via a SQL clause?
Does this dialect's LIMIT support (if any) additionally support specifying 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:setBinaryStream(long)
,
setBytes(long, byte[])
,
setBytes(long, byte[], int, int)
,
or truncate(long)
.
For CLOBs, the internal value might be changed by:
setAsciiStream(long)
,
setCharacterStream(long)
,
setString(long, String)
,
setString(long, String, int, int)
,
or 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 supportsExpectedLobUsagePattern()
.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
isAfterLast()
and
isBeforeFirst()
. Certain drivers do not
allow access to these methods for forward only cursors.
isAfterLast()
and
isBeforeFirst()
are supported for forward
only cursors; false otherwise.Does this dialect support temporary tables?
Does this dialect support `count(distinct a,b)`?
Does this dialect support UNION ALL, which is generally a faster variant of UNION?
Does this dialect support bind variables (i.e., prepared statement parameters) for its limit/offset?
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?