Sqlite: Using update => CURRENT_TIMESTAMP causes table to not be created.
Open
Nobody has claimed this yet.
docs
- Dominant language
- PHP
- Stars
- 4.5k
- Forks
- 884
- PR merge metrics
- No merged PRs in 30d
Description
There is no direct equivalent in any RDBMS other than MySQL (I think).
In Sqlite (run through PHPUnit) the table is simply not created when the update option is set to CURRENT_TIMESTAMP, without a warning or error being thrown. Works fine for MySQL though.
Maybe it should at least be listed as a MySQL only option in the documentation?
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
Start by reproducing the update => CURRENT_TIMESTAMP case through SQLite with PHPUnit and compare it with MySQL, focusing on why the table is not created and why no error is reported. Done means SQLite handles the option correctly, or the documentation clearly identifies it as MySQL-only.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mysql, php, sqlite
- Domain
- database
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100