[DiscordArchive] Had an issue with updates/authserver file from 27july25
[DiscordArchive] Had an issue with updates/authserver file from 27july25
Original source
Had an issue with updates/authserver file from 27july25
It tried to add a column I already had without checking if it already existed. Can open a PR for this later. Is it okay to update an already existing .SQL file?
rektbyfaith
08-22-2025, 03:59 PM #1Archived author: JudgeFae • Posted: 2025-08-22T15:59:02.573000+00:00
Original source
Had an issue with updates/authserver file from 27july25
It tried to add a column I already had without checking if it already existed. Can open a PR for this later. Is it okay to update an already existing .SQL file?
Original source
Need to change
> ALTER TABLE `account`
> ADD COLUMN `Flags` INT UNSIGNED NOT NULL DEFAULT '0' AFTER `expansion`;
to this
> ALTER TABLE `account`
> ADD COLUMN IF NOT EXISTS `Flags` INT UNSIGNED NOT NULL DEFAULT '0' AFTER `expansion`;
rektbyfaith
08-22-2025, 04:04 PM #2Archived author: JudgeFae • Posted: 2025-08-22T16:04:44.200000+00:00
Original source
Need to change
> ALTER TABLE `account`
> ADD COLUMN `Flags` INT UNSIGNED NOT NULL DEFAULT '0' AFTER `expansion`;
to this
> ALTER TABLE `account`
> ADD COLUMN IF NOT EXISTS `Flags` INT UNSIGNED NOT NULL DEFAULT '0' AFTER `expansion`;
Original source
Huh
rektbyfaith
08-22-2025, 06:27 PM #3Archived author: sudlud • Posted: 2025-08-22T18:27:17.502000+00:00
Original source
Huh
Original source
Why would this be necessary in a normal update progress
rektbyfaith
08-22-2025, 06:27 PM #4Archived author: sudlud • Posted: 2025-08-22T18:27:33.281000+00:00
Original source
Why would this be necessary in a normal update progress
Original source
It's not
rektbyfaith
08-22-2025, 06:29 PM #5Archived author: Revision • Posted: 2025-08-22T18:29:47.867000+00:00
Original source
It's not
Original source
Good, so no need for a pr imo
rektbyfaith
08-22-2025, 06:34 PM #6Archived author: sudlud • Posted: 2025-08-22T18:34:58.043000+00:00
Original source
Good, so no need for a pr imo
Original source
If I edit this on my machine only won't this make my local branch diverge from azerothcore master branch? I think the only way to fix this for everyone would be a pull request with the edit to check if Flags exists in account.authDB
rektbyfaith
08-22-2025, 09:29 PM #7Archived author: JudgeFae • Posted: 2025-08-22T21:29:21.401000+00:00
Original source
If I edit this on my machine only won't this make my local branch diverge from azerothcore master branch? I think the only way to fix this for everyone would be a pull request with the edit to check if Flags exists in account.authDB
Original source
I don't think I've done anything out of the ordinary to cause this error message to appear about a duplicate
rektbyfaith
08-22-2025, 09:31 PM #8Archived author: JudgeFae • Posted: 2025-08-22T21:31:24.865000+00:00
Original source
I don't think I've done anything out of the ordinary to cause this error message to appear about a duplicate
Original source
Actually just dropping flags to let the .sql remake it worked. But I don't know how I got into that situation
rektbyfaith
08-22-2025, 09:35 PM #9Archived author: JudgeFae • Posted: 2025-08-22T21:35:35.977000+00:00
Original source
Actually just dropping flags to let the .sql remake it worked. But I don't know how I got into that situation
Original source
Did you test the PR before it was merged?
It happens all the time, if you test a PR that has SQL changes, (that's not UPDATE), things that only can be ran 1 once like ALTER, you will get the error the moment you go back master (if that pr was merged)
rektbyfaith
08-22-2025, 09:41 PM #10Archived author: Ryan Turner • Posted: 2025-08-22T21:41:34.907000+00:00
Original source
Did you test the PR before it was merged?
It happens all the time, if you test a PR that has SQL changes, (that's not UPDATE), things that only can be ran 1 once like ALTER, you will get the error the moment you go back master (if that pr was merged)