Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

problem with db.sync()

See original GitHub issue

error: Uncaught (in promise) SqliteError: index email already exists

I have a subscriptions table with email as a field.

Using db.sync() causes this error. I’m not sure if I need it. It appears to work without it, but I’m not sure.

Can someone clarify the point of db.sync()

Issue Analytics

State:
Created 2 years ago
Comments:18

Top GitHub Comments

1reaction

slim-hmidicommented, Jan 7, 2022

I have the same issue, db.sync() throws an error when drop set to false.

0reactions

slim-hmidicommented, Jan 9, 2022

I created a migration file to accomplish my task (it’s not clean but it does the work) and I think that the sync method is overengineering and contains a lot of logic that makes things not easy to do. It is better to rethink the design of this function to not contain a lot of details in the background. And the migrations can be simple enough by creating a cli like knex, one for up and the other for down, and user will trigger them manually whenever he needs to update the database.