Generation Type Identity

[pwgit-create]

When you use IDENTITY, Hibernate will rely on the database's ability to automatically generate IDs through an
auto-increment column. This approach typically doesn't require creating any additional sequences or tables, as the
ID generation is handled directly by the database itself.

Here's how you can specify it in your entity class:

import javax.persistence.Entity;
import javax.persistence.GeneratedValue;
import javax.persistence.GenerationType;
import javax.persistence.Id;

@Entity
public class MyEntity {

    @Id
    @GeneratedValue(strategy = GenerationType.IDENTITY)
    private Long id;

    // other fields, getters and setters

}

With GenerationType.IDENTITY, the database will automatically increment the ID value for each new row. This is a
common strategy that works well with many relational databases like MySQL, PostgreSQL, SQL Server, etc., without
requiring additional infrastructure or configuration.

However, do note that:

1. Insert-Select Pattern: Using IDENTITY often means you need to insert the entity and then call an extra
   query to retrieve it if you want the generated ID immediately (since the ID is only available after insertion).

2. Performance Considerations: Some databases may have different performance characteristics with different
   strategies, so it's always good to benchmark based on your specific use case.

3. Batch Processing: IDENTITY might not be suitable for batch processing since the ID needs to be generated
   row by row, unlike sequence or table generators which can pre-allocate ranges of IDs.

In summary, if you want a straightforward approach that doesn't involve creating additional sequences or tables
and you're okay with the database handling ID generation, GenerationType.IDENTITY is typically an excellent
choice.