org.hibernate.id.UUIDHexGenerator id generator
but uses a RFC 4122 compliant layout (variant 2).
NOTE : Can be a bottle neck due to the need to synchronize in order to increment an internal count as part of the algorithm.
| Modifier and Type | Field and Description |
|---|---|
| private final long |
| Access | Constructor and Description |
|---|---|
| public |
| Modifier and Type | Method and Description |
|---|---|
| public static long | |
| public UUID | generateUUID(SharedSessionContractImplementor
The session asking for the generation session)Implements org. |
| public int | getGeneratedVersion()
Implements org. |
| public long | |
| public static void |
| mostSignificantBits | back to summary |
|---|---|
| private final long mostSignificantBits | |
| CustomVersionOneStrategy | back to summary |
|---|---|
| public CustomVersionOneStrategy() | |
| generateLeastSignificantBits | back to summary |
|---|---|
| public static long generateLeastSignificantBits(long seed) | |
| generateUUID | back to summary |
|---|---|
| public UUID generateUUID(SharedSessionContractImplementor session) Implements org. Doc from org. Generate the UUID.
| |
| getGeneratedVersion | back to summary |
|---|---|
| public int getGeneratedVersion() Implements org. Doc from org. Which variant, according to IETF RFC 4122, of UUID does this strategy generate? RFC 4122 defines 5 variants (though it only describes algorithms to generate 4):
Informational only, and not used at this time.
| |
| getMostSignificantBits | back to summary |
|---|---|
| public long getMostSignificantBits() | |
| main | back to summary |
|---|---|
public static void main(String[] args)
| |