Omission of precision and scale Attributes in Schema Generation

[Serhiiilnytskyi]

Flyway Version: 10.19.0
Client: Command-line, Java API, Maven plugin
Database: postgres(any version)

Problem Statement:

• When defining a BigDecimal field in a JPA entity with the @column annotation, specifying precision and scale along with a columnDefinition results in Flyway-generated schemas that omit the precision and scale attributes.

Steps to Reproduce:

• Define a JPA entity with a BigDecimal field annotated as follows:

@Column(CoreConstraints.PRECISION, scale = CoreConstraints.SCALE, columnDefinition = "DEFAULT 0.00", nullable = false)

• Use Flyway to generate the database schema.
• Observe that the resulting database column lacks the specified precision, scale and column type.

Expected Behavior:

• The generated database schema should include the specified precision and scale for the amount column, ensuring accurate data representation.

Actual Behavior:

• The generated schema defines the amount column without the specified precision and scale, potentially leading to data integrity issues.

Additional Context:

• Attempts to manually alter the database schema to include the correct precision and scale are reverted by Flyway in subsequent migrations.
• This behavior persists across different environments and database systems.
• It’s possible to avoid this behavior by defining everything in the columnDefinition explicitly, as follows:

  @Column(columnDefinition = "DECIMAL(16,2) DEFAULT 0.00", nullable = false)

However, this approach has significant drawbacks:
- It reduces code readability, making it harder for developers to understand the constraints quickly.
- It decreases consistency with other project codebases where precision and scale are specified separately for clarity and maintainability.