This implementation is not the most efficient one.
| Modifier and Type | Field and Description |
|---|---|
| private IntegralDataTypeHolder |
| Access | Constructor and Description |
|---|---|
| public | NoopOptimizer(Class<?>
The Java type of the values to be generated returnClass, int The increment size. incrementSize)Constructs a NoopOptimizer |
| Modifier and Type | Method and Description |
|---|---|
| public boolean | applyIncrementSizeToSourceValues()
Implements org. |
| public Serializable | generate(AccessCallback
Callback to access the underlying value source. callback)Implements org. |
| public IntegralDataTypeHolder | getLastSourceValue()
Implements org. |
| lastSourceValue | back to summary |
|---|---|
| private IntegralDataTypeHolder lastSourceValue | |
| NoopOptimizer | back to summary |
|---|---|
| public NoopOptimizer(Class<?> returnClass, int incrementSize) Constructs a NoopOptimizer
| |
| applyIncrementSizeToSourceValues | back to summary |
|---|---|
| public boolean applyIncrementSizeToSourceValues() Implements org. Doc from org. Are increments to be applied to the values stored in the underlying value source?
| |
| generate | back to summary |
|---|---|
| public Serializable generate(AccessCallback callback) Implements org. Doc from org. Generate an identifier value accounting for this specific optimization. All known implementors are synchronized. Consider carefully if a new implementation could drop this requirement.
| |
| getLastSourceValue | back to summary |
|---|---|
| public IntegralDataTypeHolder getLastSourceValue() Implements org. Doc from org. A common means to access the last value obtained from the underlying source. This is intended for testing purposes, since accessing the underlying database source directly is much more difficult.
| |