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.

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

Replicator migrate fails on existing database #2000

Closed
donaldinho opened this issue May 14, 2024 · 1 comment
Closed

Replicator migrate fails on existing database #2000

donaldinho opened this issue May 14, 2024 · 1 comment
Labels
s-noop Cannot be worked on

Comments

@donaldinho
Copy link

What is the bug?
Run into a number of issues while running the farcaster replicator migrate command on an existing database.

  • kysely_migration and kysely_migration_lock tables do not get created so migration fails. It's not clear whether this is because the database has existing tables in it or more specifically because there are kysely migration tables in a different schema in the database for another application
  • After creating these tables manually the migration fails because we have a table called reactions in another schema
  • Connected with this i could not see a way to put replicator tables in their own schema so had to move other tables out of the public schema to keep things seperated

How can it be reproduced? (optional)
Run migrate on a db with existing tables. We're running ponder (ponder.sh) which also has kysely migrations in the ponder schema in our db.

@github-actions github-actions bot added the s-triage Needs to be reviewed, designed and prioritized label May 14, 2024
@sds sds added s-noop Cannot be worked on and removed s-triage Needs to be reviewed, designed and prioritized labels Jun 3, 2024
@sds
Copy link
Member

sds commented Jun 3, 2024

We recommend you use the Shuttle project instead of the old replicator. There were many issues with the replicator that won't be fixed.

@sds sds closed this as completed Jun 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
s-noop Cannot be worked on
Projects
None yet
Development

No branches or pull requests

2 participants