Add package_url and arguments fields #4
Conversation
| @@ -27,7 +27,7 @@ Object.keys(db).forEach(function(modelName) { | |||
| } | |||
| }); | |||
|
|
|||
| sequelize.sync(); | |||
| sequelize.sync({force: true}); | |||
There was a problem hiding this comment.
Yes, this will drop and recreate all tables for an existing deployment. Yes, I plan to change this to a Sequelize data migration rather than just forcing the model sync on each startup.
|
Too bad there's no good way to marry model sync and migrations :person_frowning:. Though the umzug migration library the sequelize folks provide seems to give a similar interface program-wise (so it's not like having to figure out how to shoehorn in a shell execution of the sequelize cli. It'd be nice if it could provide best-guess migrations a-la EF code-first migrations, but I suppose one can't have everything. edit: Oh, but also |
with the note that we should swap out force-sync with migrations (or at least just remove force-sync) soonish before we accidentally lose actual data.Add package_url and arguments fields
Add some fields that I hadn't thought of before, but I think will prove useful.
@maclennann