Uh oh!
There was an error while loading. Please reload this page.
fix: Forge::modifyColumn() for Postgre handler - #9676
Conversation
@paulbalandan, given the recent testing challenges, do you have any thoughts on why this only happens with OCI8 and SQLSRV? Interestingly, migration locks (#9660) follow the same approach of creating a table for just one test case, but they don't seem to have these issues... |
paulbalandan
commented
Aug 13, 2025
The test fails so the cleanup isn't reached causing |
michalsn
commented
Aug 13, 2025
Idk what I was thinking... I totally missed the errors... sorry 🤦 |
14c5562 to
4721884Compare
neznaika0
left a comment
There was a problem hiding this comment.
I'm reviewing all the PR, but I don't know much for approval. It looks good.
Uh oh!
There was an error while loading. Please reload this page.
michalsn
commented
Aug 15, 2025
Thank you @paulbalandan and @neznaika0 |
Description
This PR fixes a bug in
Postgrewhere changing a column's default value viaConfig\Database\Forge::modifyColumn()would result in incorrect SQL syntax.Fixes#9671
Checklist: