Fix #1080: Protection against duplicate entries in the pa_operation_template table #1091
Conversation
...g/changesets/powerauth-java-server/1.5.x/20231018-add-constraint-operation-template-name.xml
Outdated
Show resolved
Hide resolved
...g/changesets/powerauth-java-server/1.5.x/20231018-add-constraint-operation-template-name.xml
Outdated
Show resolved
Hide resolved
...g/changesets/powerauth-java-server/1.5.x/20231018-add-constraint-operation-template-name.xml
Outdated
Show resolved
Hide resolved
...tlime/security/powerauth/app/server/database/repository/OperationTemplateRepositoryTest.java
Show resolved
Hide resolved
...curity/powerauth/app/server/service/behavior/tasks/OperationTemplateServiceBehaviorTest.java
Outdated
Show resolved
Hide resolved
| </not> | ||
| </preConditions> | ||
| <comment>Add unique constraint to pa_operation_template.template_name</comment> | ||
| <addUniqueConstraint tableName="pa_operation_template" columnNames="template_name" constraintName="pa_operation_template_template_name_uk" /> |
There was a problem hiding this comment.
@zcgandcomp Should we keep recording the db changes also in the migration guides or not?
There was a problem hiding this comment.
We should add information into the migration guide, please add this information in the usual way as seen in previous migration guides.
There was a problem hiding this comment.
Should we be concrete about the changes or just mention that some changes are needed and link a script, which will be generated during the release?
There was a problem hiding this comment.
https://github.com/wultra/development-internal/wiki/Using-Liquibase#13-migration-between-versions. Yes please add a migration guide and mention the change. In theory it is possible to have (invalid) duplicities in the DB. The migration script in SQL will be generated during release procedure.
| </not> | ||
| </preConditions> | ||
| <comment>Add unique constraint to pa_operation_template.template_name</comment> | ||
| <addUniqueConstraint tableName="pa_operation_template" columnNames="template_name" constraintName="pa_operation_template_template_name_uk" /> |
There was a problem hiding this comment.
https://github.com/wultra/development-internal/wiki/Using-Liquibase#13-migration-between-versions. Yes please add a migration guide and mention the change. In theory it is possible to have (invalid) duplicities in the DB. The migration script in SQL will be generated during release procedure.
jnpsk
deleted the
issues/1080-operation-template-table-duplicate-entries
branch
Fix #1080