You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
What is the bug?
Run into a number of issues while running the farcaster replicator migrate command on an existing database.
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.
The text was updated successfully, but these errors were encountered: