Note
Anonymous bind markers are problematic because they have to appear in generated SQL in the same order they get generated. This might cause challenges in the future with complex generate statements. For example those containing subselects which limit the freedom of arranging bind markers.
| Modifier and Type | Field and Description |
|---|---|
| private volatile int | |
| private static final AtomicIntegerFieldUpdater | |
| private final String |
| Access | Constructor and Description |
|---|---|
| pack-priv | AnonymousBindMarkers(String
parameter bind marker placeholder)Create a new |
| Modifier and Type | Method and Description |
|---|---|
| public BindMarker |
| counter | back to summary |
|---|---|
private volatile int counter
| |
| COUNTER_INCREMENTER | back to summary |
|---|---|
| private static final AtomicIntegerFieldUpdater<AnonymousBindMarkers> COUNTER_INCREMENTER | |
| placeholder | back to summary |
|---|---|
| private final String placeholder | |
| AnonymousBindMarkers | back to summary |
|---|---|
| pack-priv AnonymousBindMarkers(String placeholder) Create a new
| |
| next | back to summary |
|---|---|
| public BindMarker next() Implements org. Doc from org. Create a new
| |