IOhacker commented on PR #5764:
URL: https://github.com/apache/fineract/pull/5764#issuecomment-4315434626

   @AshharAhmadKhan I notice two items after trying to run this on an existing 
tenant,
   
   Change set author must be "fineract" and there is an issue with a Foreing 
keys, could you please raise a PR for fixing the issues reported?
   
   fineract-server-1  | Caused by: 
liquibase.exception.MigrationFailedException: Migration failed for changeset 
db/changelog/tenant/parts/0231_remove_clientcharge_inactivate_permissions.xml::1::ashharahmadkhan:
   fineract-server-1  |      Reason: liquibase.exception.DatabaseException: 
ERROR: update o delete en «m_permission» viola la llave foránea 
«fk8dedb048103b544b» en la tabla «m_role_permission»
   fineract-server-1  |   Detail: La llave (id)=(672) todavía es referida desde 
la tabla «m_role_permission». [Failed SQL: (0) DELETE FROM public.m_permission 
WHERE code='INACTIVATE_CLIENTCHARGE']
   fineract-server-1  |    at 
liquibase.changelog.ChangeSet.execute(ChangeSet.java:873)
   fineract-server-1  |    at 
liquibase.changelog.visitor.UpdateVisitor.executeAcceptedChange(UpdateVisitor.java:127)
   fineract-server-1  |    at 
liquibase.changelog.visitor.UpdateVisitor.visit(UpdateVisitor.java:71)
   fineract-server-1  |    at 
liquibase.changelog.ChangeLogIterator.lambda$run$0(ChangeLogIterator.java:133)
   fineract-server-1  |    at liquibase.Scope.lambda$child$0(Scope.java:216)
   fineract-server-1  |    at liquibase.Scope.child(Scope.java:225)
   fineract-server-1  |    at liquibase.Scope.child(Scope.java:215)
   fineract-server-1  |    at liquibase.Scope.child(Scope.java:194)
   fineract-server-1  |    at 
liquibase.changelog.ChangeLogIterator.lambda$run$1(ChangeLogIterator.java:122)
   fineract-server-1  |    at liquibase.Scope.lambda$child$0(Scope.java:216)
   fineract-server-1  |    at liquibase.Scope.child(Scope.java:225)
   fineract-server-1  |    at liquibase.Scope.child(Scope.java:215)
   fineract-server-1  |    at liquibase.Scope.child(Scope.java:194)
   fineract-server-1  |    at liquibase.Scope.child(Scope.java:282)
   fineract-server-1  |    at liquibase.Scope.child(Scope.java:286)
   fineract-server-1  |    at 
liquibase.changelog.ChangeLogIterator.run(ChangeLogIterator.java:91)
   fineract-server-1  |    ... 32 common frames omitted
   fineract-server-1  | Caused by: liquibase.exception.DatabaseException: 
ERROR: update o delete en «m_permission» viola la llave foránea 
«fk8dedb048103b544b» en la tabla «m_role_permission»
   fineract-server-1  |   Detail: La llave (id)=(672) todavía es referida desde 
la tabla «m_role_permission». [Failed SQL: (0) DELETE FROM public.m_permission 
WHERE code='INACTIVATE_CLIENTCHARGE']
   
   
   fineract-server-1  |   Detail: La llave (id)=(678) todavía es referida desde 
la tabla «m_role_permission». [Failed SQL: (0) DELETE FROM public.m_permission 
WHERE code='INACTIVATE_CLIENTCHARGE_CHECKER']
   fineract-server-1  |    at 
liquibase.executor.jvm.JdbcExecutor$ExecuteStatementCallback.doInStatement(JdbcExecutor.java:520)
   fineract-server-1  |    at 
liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:85)
   fineract-server-1  |    at 
liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:188)
   fineract-server-1  |    at 
liquibase.executor.AbstractExecutor.execute(AbstractExecutor.java:148)
   fineract-server-1  |    at 
liquibase.database.AbstractJdbcDatabase.executeStatements(AbstractJdbcDatabase.java:1198)
   fineract-server-1  |    at 
liquibase.changelog.ChangeSet.execute(ChangeSet.java:816)
   fineract-server-1  |    ... 47 common frames omitted
   fineract-server-1  | Caused by: org.postgresql.util.PSQLException: ERROR: 
update o delete en «m_permission» viola la llave foránea «fk8dedb048103b544b» 
en la tabla «m_role_permission»
   fineract-server-1  |   Detail: La llave (id)=(678) todavía es referida desde 
la tabla «m_role_permission».
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to