Closed th3l0g4n closed 9 years ago
@Jon889 @th3l0g4n, I kind of lost track of your discussion guys. Can this be merged or discarded? Thanks! :)
Hey Jan, this was an alternative approach to the one Jon introduced, so this can actually be closed. We kinda worked in the same issue at the same time :/
I think this can be discarded?
Thanks guys! :) :+1:
This should fix the DB Error on first startup of the server. The Problem is, that the "year" column is already defined in the movies model. When applying the migrations, sequelize blindly tries to add that already existing column to the Movies table.
Maybe the migration script can also be removed as the column is defined in model.