-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: [SQLite3] Forge::modifyColumn() messes up table #8457
Conversation
6db3322
to
12b6d45
Compare
@dgvirtual Can you test this? |
I would like to. How do I pull the changes into the code on my machine, what should I google for to find how its done? sth like this? |
@dgvirtual If you like CLI, I recommend https://cli.github.com/
Of course you can get from my repository: |
Hi, so I rerun the routine that I applied when filing bug report #8410. There is still one unrequested change that happens in an unreleated column, and I am not sure how bad it is; default of column with TINYINT datatype changes from integer zero to string zero:
Same happens if I change the type to INT or DECIMAL. |
576397a
to
40a84c8
Compare
@dgvirtual Thank you for testing. Before CREATE TABLE `db_invoices` (
`id` INTEGER PRIMARY KEY AUTOINCREMENT,
`user_id` INT NOT NULL,
`month` VARCHAR NOT NULL,
`invoice_series` VARCHAR NOT NULL,
`total` DECIMAL NOT NULL,
`paid` TINYINT NOT NULL DEFAULT 0,
`paid_date` VARCHAR NULL DEFAULT NULL,
`created_at` DATETIME NOT NULL,
`updated_at` DATETIME NOT NULL
) After CREATE TABLE `db_invoices` (
`id` INTEGER NULL,
`user_id` INT NOT NULL,
`month` VARCHAR NOT NULL,
`series` VARCHAR NOT NULL,
`total` DECIMAL NOT NULL,
`paid` TINYINT NOT NULL DEFAULT 0,
`paid_date` VARCHAR NULL DEFAULT NULL,
`created_at` DATETIME NOT NULL,
`updated_at` DATETIME NOT NULL,
CONSTRAINT `pk_db_invoices` PRIMARY KEY(`id`)
) |
1704a93
to
cd2d74d
Compare
cb397c0
to
8d30df7
Compare
Description
Fixes #8410
OCI8 test failure will be fixed in #8459Checklist: