| Access | Constructor and Description |
|---|---|
| public |
| Modifier and Type | Method and Description |
|---|---|
| public String | appendLockHint(LockMode
The lock mode to apply mode, String The name of the table to which to apply the lock hint. tableName)Overrides org. |
| public String | applyLocksToSql(String
the SQL string to modify sql, LockOptions lock options indexed by aliased table names. aliasedLockOptions, Map<K, V> a map of key columns indexed by aliased table names. keyColumnNames)Overrides org. |
| public boolean | forUpdateOfColumns()
Is FOR UPDATE OF syntax supported?
|
| public String | getForUpdateString()
Overrides org. |
| public String | getForUpdateString(String
The columns to be write locked. aliases)
Get the FOR UPDATE OF column_list fragment appropriate for this
dialect given the aliases of the columns to be write locked.
|
| public boolean | supportsExpectedLobUsagePattern()
Overrides org. |
| public boolean | supportsLobValueChangePropogation()
Overrides org. |
| SybaseASE157Dialect | back to summary |
|---|---|
| public SybaseASE157Dialect() | |
| appendLockHint | back to summary |
|---|---|
| public String appendLockHint(LockMode mode, String tableName) Overrides org. Doc from org. 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 Schulz | |
| applyLocksToSql | back to summary |
|---|---|
| public String applyLocksToSql(String sql, LockOptions aliasedLockOptions, Map<K, V> keyColumnNames) Overrides org. Doc from org. 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.
| |
| forUpdateOfColumns | back to summary |
|---|---|
| public boolean forUpdateOfColumns() Overrides org. Doc from org. Is FOR UPDATE OF syntax supported?
| |
| getForUpdateString | back to summary |
|---|---|
| public String getForUpdateString() Overrides org. Doc from org. Get the string to append to SELECT statements to acquire locks for this dialect.
| |
| getForUpdateString | back to summary |
|---|---|
| public String getForUpdateString(String aliases) Overrides org. Doc from org. Get the FOR UPDATE OF column_list fragment appropriate for this dialect given the aliases of the columns to be write locked. | |
| supportsExpectedLobUsagePattern | back to summary |
|---|---|
| public boolean supportsExpectedLobUsagePattern() Overrides org. Doc from org. Actually Sybase does not support LOB locators at al.
| |
| supportsLobValueChangePropogation | back to summary |
|---|---|
| public boolean supportsLobValueChangePropogation() Overrides org. Doc from org. 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:
For CLOBs, the internal value might be changed by:
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
| |