Create rules for backwards compatibility with database-specific error codes
Open
@jayfray12 is already working on this.
Since Dec 17, 2024.
kind/feature
priority/important-longterm
size/XS
spring-migration/6
spring-migration/6.0
triage/accepted
- Dominant language
- Java
- Stars
- 6
- Forks
- 49
- PR merge metrics
- No merged PRs in 30d
Description
According to the migration guide:
For full backwards compatibility with database-specific error codes, consider re-enabling the legacy SQLErrorCodeSQLExceptionTranslator. This translator kicks in for user-provided sql-error-codes.xml files. It can simply pick up Spring's legacy default error code mappings as well when triggered by an empty user-provided file in the root of the classpath.
Investigate and create rules if necessary.
In the rule description and message, try to be as verbose and clear as possible. Code examples are always welcome and useful. Feel free to use markdown syntax for these.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.