Changes:
Types.TIMESTAMP changed from "timestamp with time zone" to "timestamp(9) with time zone"| Modifier and Type | Field and Description |
|---|---|
| private static final LimitHandler |
| Access | Constructor and Description |
|---|---|
| public |
| Modifier and Type | Method and Description |
|---|---|
| public boolean | doesReadCommittedCauseWritersToBlockReaders()
Overrides org. |
| public boolean | doesRepeatableReadCauseReadersToBlockWriters()
Overrides org. |
| public boolean | forUpdateOfColumns()
Is FOR UPDATE OF syntax supported?
|
| public String | getCurrentTimestampSelectString()
Overrides org. |
| public String | getCurrentTimestampSQLFunctionName()
Overrides org. |
| public LimitHandler | |
| public IdentityColumnSupport | getIdentityColumnSupport()
Overrides org. IdentityColumnSupport
|
| public String | getLimitString(String
The query to which to apply the limit. querySelect, int The offset of the limit offset, int The limit of the limit ;) limit)Overrides org. |
| public String | getQuerySequencesString()
Overrides org. |
| public boolean | isCurrentTimestampSelectStringCallable()
Overrides org. getCurrentTimestampSelectString
be treated as callable.
|
| protected void | |
| protected void | |
| public boolean | supportsCurrentTimestampSelection()
Overrides org. |
| public boolean | supportsLimitOffset()
Overrides org. |
| public boolean | supportsOuterJoinForUpdate()
Overrides org. |
| public boolean | supportsPooledSequences()
Overrides org. |
| public boolean | supportsUnionAll()
Does this dialect support UNION ALL, which is generally a faster
variant of UNION?
|
| public boolean | supportsVariableLimit()
Overrides org. |
| public boolean | useMaxForLimit()
Overrides org. |
| LIMIT_HANDLER | back to summary |
|---|---|
| private static final LimitHandler LIMIT_HANDLER | |
| Ingres9Dialect | back to summary |
|---|---|
| public Ingres9Dialect() Constructs a Ingres9Dialect | |
| doesReadCommittedCauseWritersToBlockReaders | back to summary |
|---|---|
| public boolean doesReadCommittedCauseWritersToBlockReaders() Overrides org. Doc from org. For the underlying database, is READ_COMMITTED isolation implemented by forcing readers to wait for write locks to be released?
| |
| doesRepeatableReadCauseReadersToBlockWriters | back to summary |
|---|---|
| public boolean doesRepeatableReadCauseReadersToBlockWriters() Overrides org. Doc from org. For the underlying database, is REPEATABLE_READ isolation implemented by forcing writers to wait for read locks to be released?
| |
| forUpdateOfColumns | back to summary |
|---|---|
| public boolean forUpdateOfColumns() Overrides org. Doc from org. Is FOR UPDATE OF syntax supported?
| |
| getCurrentTimestampSelectString | back to summary |
|---|---|
| public String getCurrentTimestampSelectString() Overrides org. Doc from org. Retrieve the command used to retrieve the current timestamp from the database. | |
| getCurrentTimestampSQLFunctionName | back to summary |
|---|---|
| public String getCurrentTimestampSQLFunctionName() Overrides org. Doc from org. The name of the database-specific SQL function for retrieving the current timestamp. | |
| getDefaultLimitHandler | back to summary |
|---|---|
| public LimitHandler getDefaultLimitHandler() Overrides org.
| |
| getIdentityColumnSupport | back to summary |
|---|---|
| public IdentityColumnSupport getIdentityColumnSupport() Overrides org. Doc from org. Get the appropriate
| |
| getLimitString | back to summary |
|---|---|
| public String getLimitString(String querySelect, int offset, int limit) Overrides org. Doc from org. Given a limit and an offset, apply the limit clause to the query. | |
| getQuerySequencesString | back to summary |
|---|---|
| public String getQuerySequencesString() Overrides org. Doc from org. Get the select command used retrieve the names of all sequences. | |
| isCurrentTimestampSelectStringCallable | back to summary |
|---|---|
| public boolean isCurrentTimestampSelectStringCallable() Overrides org. Doc from org. Should the value returned by
| |
| registerDateTimeColumnTypes | back to summary |
|---|---|
| protected void registerDateTimeColumnTypes() Register column types date, time, timestamp | |
| registerDateTimeFunctions | back to summary |
|---|---|
| protected void registerDateTimeFunctions() Register functions current_time, current_timestamp, current_date | |
| supportsCurrentTimestampSelection | back to summary |
|---|---|
| public boolean supportsCurrentTimestampSelection() Overrides org. Doc from org. Does this dialect support a way to retrieve the database's current timestamp value?
| |
| supportsLimitOffset | back to summary |
|---|---|
| public boolean supportsLimitOffset() Overrides org. Doc from org. Does this dialect's LIMIT support (if any) additionally support specifying an offset?
| |
| supportsOuterJoinForUpdate | back to summary |
|---|---|
| public boolean supportsOuterJoinForUpdate() Overrides org. Doc from org. Does this dialect support FOR UPDATE in conjunction with outer joined rows?
| |
| supportsPooledSequences | back to summary |
|---|---|
| public boolean supportsPooledSequences() Overrides org. Doc from org. Does this dialect support "pooled" sequences. Not aware of a better name for this. Essentially can we specify the initial and increment values?
| |
| supportsUnionAll | back to summary |
|---|---|
| public boolean supportsUnionAll() Overrides org. Doc from org. Does this dialect support UNION ALL, which is generally a faster variant of UNION?
| |
| supportsVariableLimit | back to summary |
|---|---|
| public boolean supportsVariableLimit() Overrides org. Doc from org. Does this dialect support bind variables (i.e., prepared statement parameters) for its limit/offset?
| |
| useMaxForLimit | back to summary |
|---|---|
| public boolean useMaxForLimit() Overrides org. Doc from org. 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?
| |