Analysis and Solutions for Hibernate "Field 'id' doesn't have a default value" Error

Problem Phenomenon and Error Analysis

When using Hibernate for data persistence operations, developers frequently encounter the "Field 'id' doesn't have a default value" exception. This error typically occurs when attempting to insert new records, where the system fails to generate valid values for the entity class's primary key field. From the error stack trace, this is clearly a JDBC exception indicating that the database rejected the insert operation because the primary key field lacks a default value.

Consider the following entity class definition example:

@Entity
@Inheritance(strategy = InheritanceType.JOINED)
public class Mensagem {
    protected Long id;
    
    protected Mensagem() { }
    
    @Id
    @GeneratedValue
    public Long getId() {
        return id;
    }
    
    public Mensagem setId(Long id) {
        this.id = id;
        return this;
    }
}

In the corresponding database operation code:

SessionFactory factory = new AnnotationConfiguration()
    .configure()
    .buildSessionFactory();

Session session = factory.openSession();
Transaction tx = session.beginTransaction();

Mensagem msg = new Mensagem("YARR!");
session.save(msg);

tx.commit();
session.close();

Root Cause Investigation

The core issue lies in the inconsistency between entity class mapping and database table structure. Although the code uses @GeneratedValue annotation to indicate automatic primary key generation, the database table might not be properly configured with auto-increment constraints. In MySQL databases, the primary key field must explicitly include the AUTO_INCREMENT attribute; otherwise, even if Hibernate attempts to generate primary key values, the database will reject them.

The correct MySQL table creation statement should include:

CREATE TABLE mensagem (
    id BIGINT NOT NULL AUTO_INCREMENT,
    -- other field definitions
    PRIMARY KEY (id)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

Solutions and Best Practices

When encountering such problems, the most effective solution is to recreate the database and regenerate the table structure using the SchemaExport tool. This approach ensures complete consistency between the database schema and entity class mapping.

Specific implementation steps:

// Configure Hibernate for automatic schema export
Configuration cfg = new AnnotationConfiguration()
    .configure();
cfg.setProperty("hibernate.hbm2ddl.auto", "create");

// Use SchemaExport to generate database structure
SchemaExport export = new SchemaExport(cfg);
export.create(true, true);

For scenarios requiring finer control, explicitly specify the primary key generation strategy in the entity class:

@Entity
public class Supplier {
    @Id
    @GeneratedValue(strategy = GenerationType.IDENTITY)
    @Column(name = "ID")
    private Long id;
    
    // Other fields and methods
}

Database Compatibility Considerations

Different database systems exhibit variations in primary key generation mechanisms. Oracle databases typically use sequences for primary key value generation, while MySQL relies on AUTO_INCREMENT features. Developers need to adjust configuration strategies based on the actual database type being used.

For MySQL environments, ensure:

• Primary key field is defined as AUTO_INCREMENT
• Use GenerationType.IDENTITY strategy
• Table engine supports auto-increment functionality (e.g., InnoDB)

Preventive Measures and Debugging Techniques

To prevent similar issues, recommended practices during development include:

1. Using version control for database migration scripts
2. Thoroughly validating schema updates in test environments
3. Regularly checking consistency between database table structure and entity mapping
4. Using database management tools to directly verify table constraints

When problems occur, diagnostic steps include:

// Check database metadata for current session
DatabaseMetaData metaData = session.connection().getMetaData();
ResultSet rs = metaData.getColumns(null, null, "mensagem", "id");
while (rs.next()) {
    String isAutoIncrement = rs.getString("IS_AUTOINCREMENT");
    System.out.println("ID field auto increment: " + isAutoIncrement);
}

Through systematic analysis and proper configuration practices, developers can effectively avoid the "Field 'id' doesn't have a default value" error and ensure stable operation of Hibernate applications.