WordPress / WordPress/sqlite-database-integration
Refactor data type maps and fine tune column metadata
Open
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 363
- Forks
- 67
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 7
Description
As a follow-up on https://github.com/WordPress/sqlite-database-integration/pull/209, there are a few small improvements to be done.
- Currently, we already have multiple maps in the form of
mysql-type-to-something. We can consolidate them into something like this:
- The column metadata information can be made a bit more accurate. Namely—adding support for MySQLi flags and possibly improving some edge cases.
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 reviewing pull request 209 and locating the existing mysql-type-to-* maps. Then inspect the column metadata handling for MySQLi flags and the mentioned edge cases. Done means the maps are consolidated and column metadata is more accurate, with the relevant behavior covered by the project's existing checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mysql, php, sqlite
- Domain
- database
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100