Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

5 unique constraint limit #1547

Closed
linuxninja39 opened this issue Nov 18, 2020 · 1 comment
Closed

5 unique constraint limit #1547

linuxninja39 opened this issue Nov 18, 2020 · 1 comment

Comments

@linuxninja39
Copy link

linuxninja39 commented Nov 18, 2020

Environment

Liquibase Version: 4.1.0

Liquibase Integration & Version: gradle-6.7

Liquibase Extension(s) & Version: liquibase-hibernate5-4.1.0

Database Vendor & Version:mariadb-10.3

Operating System Type & Version: ubuntu 20.20

Description

A clear and concise description of the issue being addressed.
When I add a 6th unique constraint, diffChangeLog will keep creating the 6th+ constraint over and over.

Steps To Reproduce

Create 5 entities with Entity and @column(unique = true) or a Table annotation with a combined unique constraint.
Do a generateChangeLog.
Do an update, everything should work
Now create a 6th Entity with a unique constraint
Do diffChangeLog. Now if you look you'll see of of your unique constraints has been reproduced and your update will fail because of a duplicate key

Actual Behavior

  • changeSet:
    id: 1605725708662-2
    author: jacob (generated)
    changes:
    • addUniqueConstraint:
      columnNames: qool
      constraintName: UC_QOOLNESSQOOL_COL
      tableName: qoolness

and

  • changeSet:
    id: 1605725812015-1
    author: jacob (generated)
    changes:
    • addUniqueConstraint:
      columnNames: qool
      constraintName: UC_QOOLNESSQOOL_COL
      tableName: qoolness

Expected/Desired Behavior

Should be able to have as many unique constraints in my schema as I'd like.

Screenshots (if appropriate)

If applicable, add screenshots to help explain your problem.

Additional Context

Add any other context about the problem here.

@nvoxland
Copy link
Contributor

Thanks for the report.
This will be fixed in 4.2.1 as #1477.

Closing this as a duplicate

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants