Table not created during migration
Open
Nobody has claimed this yet.
bug
waiting on feedback
- Dominant language
- PHP
- Stars
- 4.5k
- Forks
- 884
- PR merge metrics
- No merged PRs in 30d
Description
If I use the following:
$table->addColumn('modified_at', 'timestamp', [
'null' => false,
'default' => 'CURRENT_TIMESTAMP',
'update' => 'CURRENT_TIMESTAMP',
'precision' => 4,
]);
The use of update causes the migration of the entire table to fail.
Tested with SQLite as the database engine.
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 migration with SQLite and the shown addColumn options, focusing on how the update option is handled. Trace the migration path for table creation and compare the generated SQLite operation with the expected result. Done means the table is created successfully when update is specified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, sqlite
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100