spring-projects / spring-projects/spring-tools
SQL syntax validation
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 983
- Forks
- 240
- Avg merge
- 7d 1h
- Merged PRs (30d)
- 7
Description
Currently MySQL grammar is used for semantic tokens and syntax validation for the native queries.
However, there are more flavours of SQL available: PostGres, MariaDB, etc (see https://github.com/antlr/grammars-v4/tree/master/sql)
Perhaps an inference can be made from the classpath JARs to indicate which SQL parser should be used... Perhaps we may want to opt out from supporting native query syntax validation completely (too much for a rather limited use case), perhaps the same is true for semantic tokens... The most commonly used ones might be supported and for the rest no syntax validation... TBD
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.
Research direction
No files, tests, or entry points are named. Start by locating the native-query semantic-token and syntax-validation handling; the issue does not define which SQL dialects or opt-out behavior would constitute done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mariadb, mysql, postgresql, sql
- Domain
- databases, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100