We're updating the issue view to help you get more done. 

Filter XML sql-type to avoid passing identity-column data types when using a columnDefinition

Description

When a user defines an entity mapping as follows, Envers will simply take the provided columnDefinition and pass it as-is to the XML binding for the audit table.

1 2 3 @Generated(GenerationTime.INSERT) @Column(columnDefinition = "integer auto_increment") private int caseNumber;

Rather than having the XML binding contain sql-type="integer auto_increment', the binding should actually read sql-type="integer".

Perhaps dialects can influence what to filter by consulting the IdentityColumnSupport?

Environment

None

Status

Assignee

Chris Cranford

Reporter

Chris Cranford

Fix versions

Labels

None

backPortable

None

Suitable for new contributors

None

Requires Release Note

None

Pull Request

None

backportDecision

None

Components

Affects versions

5.2.0

Priority

Major