[DiscordArchive] Too much issues with this table. Something wrong with it's commit?
[DiscordArchive] Too much issues with this table. Something wrong with it's commit?
Original source
Too much issues with this table. Something wrong with it's commit?
rektbyfaith
05-08-2022, 04:52 PM #1Archived author: Bogir • Posted: 2022-05-08T16:52:40.690000+00:00
Original source
Too much issues with this table. Something wrong with it's commit?
Original source
![[Image: unknown.png?ex=690c29b0&is=690ad830&hm=5...7d5c2a213&]](https://cdn.discordapp.com/attachments/284406375495368704/972903978180440124/unknown.png?ex=690c29b0&is=690ad830&hm=5740c92fae59b16d9c7d3ee8c47c15921db902557f284324c45da837d5c2a213&)
rektbyfaith
05-08-2022, 04:53 PM #2Archived author: Bogir • Posted: 2022-05-08T16:53:04.161000+00:00
Original source
Original source
Happens if you skip through the squash commit
rektbyfaith
05-08-2022, 04:53 PM #3Archived author: Nyeriah • Posted: 2022-05-08T16:53:07.566000+00:00
Original source
Happens if you skip through the squash commit
Original source
If you apply the database squash before applying the SQL, the physical file gets moved before it has a chance to update the database
rektbyfaith
05-08-2022, 04:54 PM #4Archived author: Nyeriah • Posted: 2022-05-08T16:54:06.915000+00:00
Original source
If you apply the database squash before applying the SQL, the physical file gets moved before it has a chance to update the database
Original source
Have to track the commit and apply the sql manually. Or drop the databases and repopulate them. I’m afraid there’s not much that can be done about this
rektbyfaith
05-08-2022, 04:55 PM #5Archived author: Nyeriah • Posted: 2022-05-08T16:55:05.738000+00:00
Original source
Have to track the commit and apply the sql manually. Or drop the databases and repopulate them. I’m afraid there’s not much that can be done about this
Original source
answer to your question: no.
rektbyfaith
05-08-2022, 04:56 PM #6Archived author: Kitzunu • Posted: 2022-05-08T16:56:14.194000+00:00
Original source
answer to your question: no.
Original source
Another question - is there any specific steps we should be taking for server shutdown?
It looks like ^C'ing the docker initiates a sane shutdown, but figured it's worth checking before I corrupt my db over something silly
rektbyfaith
05-08-2022, 05:07 PM #7Archived author: Panoptic • Posted: 2022-05-08T17:07:57.307000+00:00
Original source
Another question - is there any specific steps we should be taking for server shutdown?
It looks like ^C'ing the docker initiates a sane shutdown, but figured it's worth checking before I corrupt my db over something silly
Original source
how could this happen if i only ever use `./acore.sh db-assembler import-updates`
rektbyfaith
05-08-2022, 05:07 PM #8Archived author: Goose • Posted: 2022-05-08T17:07:59.595000+00:00
Original source
how could this happen if i only ever use `./acore.sh db-assembler import-updates`
Original source
use automatic updater.
rektbyfaith
05-08-2022, 05:09 PM #9Archived author: Kitzunu • Posted: 2022-05-08T17:09:37.251000+00:00
Original source
use automatic updater.
Original source
You're at reivision ABC
- Update file is in /world/updates
---
Squash happens at revision DEF
---
You update to revision GHI
- File gets moved to /archived/updates
You run the assembler
- File is no longer there, so it doesn't get imported
rektbyfaith
05-08-2022, 05:09 PM #10Archived author: Nyeriah • Posted: 2022-05-08T17:09:50.993000+00:00
Original source
You're at reivision ABC
- Update file is in /world/updates
---
Squash happens at revision DEF
---
You update to revision GHI
- File gets moved to /archived/updates
You run the assembler
- File is no longer there, so it doesn't get imported
1 Guest(s)
1 Guest(s)