WordPress / WordPress/sqlite-database-integration
Review query escaping and add test coverage
Open
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 363
- Forks
- 67
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 7
Description
Review strings escaping in the MySQL lexer and SQLite driver, and add a comprehensive test suite.
- Verify string literal escaping (https://github.com/Automattic/sqlite-database-integration/pull/1#discussion_r1935826325).
- Add a comprehensive test suite (https://github.com/Automattic/sqlite-database-integration/pull/1#discussion_r1935822420).
- Consider unescaping MySQL queries in lexer (https://github.com/Automattic/sqlite-database-integration/pull/1#discussion_r1935819358).
Contributor guide
No contributing guide indexed for this repository
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
Start by reading the MySQL lexer and SQLite driver, then review the linked pull-request discussions about string literal escaping and query unescaping. Identify the existing tests covering these paths and expand them into the requested comprehensive suite. Done means escaping behavior is verified for both components and the discussed MySQL unescaping question is resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mysql, php, sqlite
- Domain
- databases, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100