org.springframework.jdbc.BadSqlGrammarException: StatementCallback; bad SQL grammar [delete from "poweratuat"."indivi_exit_compensation_in_case_exit"
using "poweratuat"."indivi_exit_compensation_in_case"
where "poweratuat"."indivi_exit_compensation_in_case_exit".id = "poweratuat"."indivi_exit_compensation_in_case".id
and "poweratuat"."indivi_exit_compensation_in_case".program_exit_date_time is null;]
at org.springframework.jdbc.support.SQLStateSQLExceptionTranslator.doTranslate(SQLStateSQLExceptionTranslator.java:99)
at org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:70)
at org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:79)
at org.springframework.jdbc.core.JdbcTemplate.translateException(JdbcTemplate.java:1538)
at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:393)
at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:431)
Tech analysis:
The program enrolment table name is not always a substring of program exit table name like coded here
In power org, exit table is truncated table name, and enrolment table is full name without any truncation.
Similar case for encounter cancel table names like coded here
AC:
The ETLs of power and poweratuat in prerelease should pass after the fix
Create general encounter type with name 'maternity benefit claims documentationaaaaaaaaaaaa' for subject type 'Individual' and check for the case in this card. Applicable for program encounter as well.
This and this cards AC should continue to work as expected.
Questions:
exit and cancel suffixes added at two places when truncated. - just by searching for exit we can find the usage
Test suggestions
Good to test with few orgs which has exit table issue(power org has this) and general encounter/program encounter issue and normal case as well is my opinion.
Issue:
Tech analysis:
AC:
Questions:
exit and cancel suffixes added at two places when truncated. - just by searching for exit we can find the usage
Test suggestions
Good to test with few orgs which has exit table issue(power org has this) and general encounter/program encounter issue and normal case as well is my opinion.