Prev Class | Next Class | Frames | No Frames |
Summary: Nested | Field | Method | Constr | Detail: Nested | Field | Method | Constr |
java.lang.Object
org.hibernate.dialect.Dialect
org.hibernate.dialect.InterbaseDialect
org.hibernate.dialect.FirebirdDialect
public class FirebirdDialect
extends InterbaseDialect
Field Summary |
Fields inherited from class org.hibernate.dialect.Dialect | |
CLOSED_QUOTE , DEFAULT_BATCH_SIZE , NO_BATCH , QUOTE |
Method Summary | |
boolean |
|
boolean |
|
String |
|
String |
|
public boolean bindLimitParametersFirst()
Does the LIMIT clause come at the start of the SELECT statement, rather than at the end?
- Overrides:
- bindLimitParametersFirst in interface InterbaseDialect
- Returns:
- true if limit parameters should come before other parameters
public boolean bindLimitParametersInReverseOrder()
ANSI SQL defines the LIMIT clause to be in the form LIMIT offset, limit. Does this dialect require us to bind the parameters in reverse order?
- Overrides:
- bindLimitParametersInReverseOrder in interface InterbaseDialect
- Returns:
- true if the correct order is limit, offset
public String getDropSequenceString(String sequenceName)
Typically dialects which support sequences can drop a sequence with a single command. This is convenience form ofDialect.getDropSequenceStrings(String)
to help facilitate that. Dialects which support sequences and can drop a sequence in a single command need *only* override this method. Dialects which support sequences but require multiple commands to drop a sequence should instead overrideDialect.getDropSequenceStrings(String)
.
- Overrides:
- getDropSequenceString in interface InterbaseDialect
- Parameters:
sequenceName
- The name of the sequence
- Returns:
- The sequence drop commands
public String getLimitString(String sql, boolean hasOffset)
Apply s limit clause to the query. Typically dialects utilizevariable
limit caluses when they support limits. Thus, when building the select command we do not actually need to know the limit or the offest since we will just be using placeholders. Here we do still pass along whether or not an offset was specified so that dialects not supporting offsets can generate proper exceptions. In general, dialects will override one or the other of this method andDialect.getLimitString(String,int,int)
.
- Overrides:
- getLimitString in interface InterbaseDialect
- Parameters:
hasOffset
- Is the query requesting an offset?
- Returns:
- the modified SQL