|Home >> All >> org >> hibernate >> [ dialect Javadoc ]|
|||org.hibernate.dialect.function.* (9)||||org.hibernate.dialect.lock.* (3)|
org.hibernate.dialect: Javadoc index of package org.hibernate.dialect.
TypeNames: This class maps a type to names. Associations may be marked with a capacity. Calling the get() method with a type and actual size n will return the associated name with smallest capacity >= n, if available and an unmarked default type otherwise. Eg, setting names.put(type, "TEXT" ); names.put(type, 255, "VARCHAR($l)" ); names.put(type, 65534, "LONGVARCHAR($l)" ); will give you back the following: names.get(type) // --> "TEXT" (default) names.get(type, 100) // --> "VARCHAR(100)" (100 is in [0:255]) names.get(type, 1000) // --> "LONGVARCHAR(1000)" (1000 is in [256:65534]) names.get(type, 100000) ...
FrontBaseDialect: An SQL Dialect for Frontbase. Assumes you're using the latest version of the FrontBase JDBC driver, available from http://frontbase.com/ NOTE : The latest JDBC driver is not always included with the latest release of FrontBase. Download the driver separately, and enjoy the informative release notes. This dialect was tested with JDBC driver version 2.3.1. This driver contains a bug that causes batches of updates to fail. (The bug should be fixed in the next release of the JDBC driver.) If you are using JDBC driver 2.3.1, you can work-around this problem by setting the following in your hibernate.properties ...
SQLFunctionTemplate: Represents HQL functions that can have different representations in different SQL dialects. E.g. in HQL we can define function concat(?1, ?2) to concatenate two strings p1 and p2. Target SQL function will be dialect-specific, e.g. (?1 || ?2) for Oracle, concat(?1, ?2) for MySql, (?1 + ?2) for MS SQL. Each dialect will define a template as a string (exactly like above) marking function parameters with '?' followed by parameter's index (first index is 1).
ProgressDialect: An SQL dialect compatible with Progress 9.1C Connection Parameters required: hibernate.dialect org.hibernate.sql.ProgressDialect hibernate.driver com.progress.sql.jdbc.JdbcProgressDriver hibernate.url jdbc:JdbcProgress:T:host:port:dbname;WorkArounds=536870912 hibernate.username username hibernate.password password The WorkArounds parameter in the URL is required to avoid an error in the Progress 9.1C JDBC driver related to PreparedStatements.
TimesTenDialect: A SQL dialect for TimesTen 5.1. Known limitations: joined-subclass support because of no CASE support in TimesTen No support for subqueries that includes aggregation - size() in HQL not supported - user queries that does subqueries with aggregation No CLOB/BLOB support No cascade delete support. No Calendar support No support for updating primary keys.
LockingStrategy: A strategy abstraction for how locks are obtained in the underlying database. All locking provided implemenations assume the underlying database supports (and that the connection is in) at least read-committed transaction isolation. The most glaring exclusion to this is HSQLDB which only offers support for READ_UNCOMMITTED isolation.
Dialect: Represents a dialect of SQL implemented by a particular RDBMS. Subclasses implement Hibernate compatibility with different systems. Subclasses should provide a public default constructor that register() a set of type mappings and default Hibernate properties. Subclasses should be immutable.
SQLFunction: Provides support routines for the HQL functions as used in the various SQL Dialects Provides an interface for supporting various HQL functions that are translated to SQL. The Dialect and its sub-classes use this interface to provide details required for processing of the function.
StandardSQLFunction: Provides a standard implementation that supports the majority of the HQL functions that are translated to SQL. The Dialect and its sub-classes use this class to provide details required for processing of the associated function.
SelectLockingStrategy: A locking strategy where the locks are obtained through select statements. For non-read locks, this is achieved through the Dialect's specific SELECT ... FOR UPDATE syntax.
MimerSQLDialect: An Hibernate 3 SQL dialect for Mimer SQL. This dialect requires Mimer SQL 9.2.1 or later because of the mappings to NCLOB, BINARY, and BINARY VARYING.
UpdateLockingStrategy: A locking strategy where the locks are obtained through update statements. This strategy is not valid for read style locks.
InformixDialect: Informix dialect. Seems to work with Informix Dynamic Server Version 7.31.UD3, Informix JDBC driver version 2.21JC3.
HSQLDialect: An SQL dialect compatible with HSQLDB (Hypersonic SQL). Note this version supports HSQLDB version 1.8 and higher, only.
VarArgsSQLFunction: Support for slightly more general templating than StandardSQLFunction , with an unlimited number of arguments.
DB2390Dialect: An SQL dialect for DB2/390. This class provides support for DB2 Universal Database for OS/390, also known as DB2/390.
SybaseAnywhereDialect: SQL Dialect for Sybase Anywhere extending Sybase (Enterprise) Dialect (Tested on ASA 8.x)
Sybase11Dialect: A SQL dialect suitable for use with Sybase 11.9.2 (specifically: avoids ANSI JOIN syntax)
NvlFunction: Emulation of coalesce() on Oracle, using multiple nvl() calls
CastFunction: ANSI-SQL style cast(foo as type) where the type is a Hibernate type
GenericDialect: A generic SQL dialect which may or may not work on any actual databases
Oracle9Dialect: An SQL dialect for Oracle 9 (uses ANSI-style syntax where possible).