Closed nobodyiam closed 2 weeks ago
In version 2.3.0 of Apollo, a critical fix was implemented to resolve SQL errors associated with the configuration retention feature in MySQL. This involved updating SQL delete statements in entity classes to properly escape table names using backticks (`).
Files | Change Summary |
---|---|
apollo-biz/src/.../AccessKey.java, .../Audit.java, ... | Updated SQL delete statements to include backticks around table names to ensure SQL compatibility. |
apollo-common/src/.../App.java, .../AppNamespace.java | Adjusted SQL delete statements to use backticks for table names in the @SQLDelete annotation. |
apollo-portal/src/.../Consumer.java, .../Permission.java, ... | Modified SQL delete statements to correctly reference table names with backticks for integrity. |
Objective (Issue #5161) | Addressed | Explanation |
---|---|---|
Fix error in SQL syntax for MySQL compatibility | ✅ | |
Ensure all affected entity classes have updated SQL | ✅ |
In a world of tables where queries might fail,
SQL syntax errors would often prevail.
Apollo now escapes with backticks in place,
Making sure all deletes run with grace.
A fix for retention, debugged and refined,
Version 2.3.0, stability you'll find.
🐇✨
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
Thanks for this fix
What's the purpose of this PR
Fix the release retention error
Which issue(s) this PR fixes:
Fixes #5161
Brief changelog
@SQLDelete
statementsFollow this checklist to help us incorporate your contribution quickly and easily:
mvn clean test
to make sure this pull request doesn't break anything.CHANGES
log.Summary by CodeRabbit
Bug Fixes
Refactor