- Shipped
- 29 மே, 2026 அன்று 1:22 AM UTC
- Author
- Kamo
- Commit
- d14dc54
KamoInitializerService failed to boot because two @Entity classes named 'Loan' and two repository classes named 'LoanRepository' both wanted to register the same JPA entity name, the same physical table 'loans', and the same Spring bean 'loanRepository': - **************** (the existing mortgage Loan entity, table LOANS) - **************** (the new personal-loans entity, was table 'loans') Fix on the personal-loans side without forcing a 60+ KamoLOS callsite refactor: - @Entity(name = "PersonalLoan") — distinct JPA entity name for JPQL - @Table(name = "personal_loans") — distinct physical table; renamed the four composite indexes to idx_personal_loans_* accordingly - **************** on LoanRepository — distinct Spring bean name The Java class names stay 'Loan' and 'LoanRepository' inside their own package, so existing imports and usages in KamoLOS remain unchanged. 36 KamoLOS tests still passing.