Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Improve gochan-migration #105

Open
2 of 7 tasks
Eggbertx opened this issue Jul 30, 2024 · 4 comments
Open
2 of 7 tasks

Improve gochan-migration #105

Eggbertx opened this issue Jul 30, 2024 · 4 comments
Assignees
@Eggbertx
Labels
gochan-migration An issue or PR related to the migration tool much work ongoing An ongoing issue that should not be marked stale plugins An issue related to gochan's plugin system

Comments

@Eggbertx
Copy link
Collaborator

Eggbertx commented Jul 30, 2024 •
edited
Loading

  • Finish implementing pre-2021 DB migration to new database
  • Implement pre-2021 DB migration in place
  • Implement Kusaba X migration to new database
  • Implement Kusaba X migration in place
  • Implement TinyBoard migration to new database
  • Implement TinyBoard migration in place
  • Add the ability for plugins to extend gochan-migration
@Eggbertx Eggbertx self-assigned this Jul 30, 2024
@Eggbertx Eggbertx added plugins An issue related to gochan's plugin system gochan-migration An issue or PR related to the migration tool much work labels Jul 30, 2024
@github-actions GitHub Actions
Copy link

This issue is stale because it has been open for 150 days with no activity.

@Eggbertx Eggbertx added ongoing An ongoing issue that should not be marked stale and removed no-issue-activity labels Dec 30, 2024
@onihilist
Copy link
Contributor

in the first comment, checkbox are up to date ?

@Eggbertx
Copy link
Collaborator Author

They are. I split them into separate tasks for migrating to a new database (or the same but with a different table prefix) and migrating in place (altering the schema to be gochan compatible). Though after doing some more testing, migrating in place might not be feasible, since it can lead to compatibility issues, especially with SQLite

@Eggbertx
Copy link
Collaborator Author

Eggbertx commented Feb 2, 2025

As a workaround for in-place migration, it now renames the tables and then treats it as if it wasn't an in-place migration, recreating the tables and populating them.
That way, the data is all there, and it has foreign key constraints

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Eggbertx Eggbertx

Labels
gochan-migration An issue or PR related to the migration tool much work ongoing An ongoing issue that should not be marked stale plugins An issue related to gochan's plugin system
Projects
None yet
Milestone
No milestone
Development

When branches are created from issues, their pull requests are automatically linked.

pre2021-migration-update gochan-org/gochan
2 participants
@Eggbertx @onihilist