Sequelize vs Typeorm

[Zeko369]

@Zeko369 I'm down to use TypeORM but we should loop @QuincyLarson into this conversation as I believe it was he who initially proposed sequelize.

Originally posted by @timmyichen in #162 (comment)

Since using TS for migrations and seeds with sequelize is a really janky experience I think that we should consider using TypeORM. If anyone has any experience using Typeorm or why we should stick with Sequelize feel free to comment here.
One great thing that we cant do with sequelize since we're using sequelize-ts for models is migrations, TypeORM can be used to automaticly generate migrations (they can sometimes be wrong, this aint Rails' ActiveRecord) but would greatly help.

[Zeko369]

Or maybe something like this Vincit/objection.js#1069 (comment)

[Zeko369]

Copied from discord
The only difference that I found so far (I'm using it for a differenet project) is that you cant do this

User.create({
    username: 'janedoe',
    birthday: new Date(1980, 6, 20)
  }))

And have to do

const user = new User();
user.username = 'asd';
user.birthday = new Date();
user.save();

But we could do this typeorm/typeorm#3903, and fix that problem

[timmyichen]

Since we're writing code that closely resembles TypeORM already, I think we can just move to that and use the linked issue above for keeping the same style.

[Zeko369]

@nik-john @ceciliaconsta3 @allella @QuincyLarson

[allella]

I'm fine with whatever you folks find will work. Though, I agree it would be good for Quincy and others to stamp this one.

Given the trouble Sequelize + Typescript has already caused it seems wise to consider a tool that plays well.

Sequelize was suggested by Quincy well before the technical conversations started, presumably to set a reasonable default tech stack and avoid an endless conversation about the stack.

Also, Sequelize was suggested before TypeScript was introduced.

[QuincyLarson]

I will defer to the people building the app itself.

@Zeko369 If you think TypeORM is a better fit and you're the main person working on this at the moment, I say go ahead and get started with it.

If anyone has other opinions on this you can share those here.

[Zeko369]

@freeCodeCamp/chapter-moderators Any other thoughts?

[allella]

@nik-john @ceciliaconsta3 you were both referenced here and are welcome to chime in. I think everybody else on the thread has stated their opinion or deferred (Quincy and I).

@iansltx listed both TS and Sequelize in #11 and @oyewoas @hamidnoei @imccausl listed Sequelize experience, so if there's any final words on using TypeORM, instead of Sequelize, then please comment now.

[Zeko369]

Tnx @allella for finding and pinging them 👍

[ceciliaconsta3]

$0.02: As Quincy mentioned earlier, whoever is planning to perform the bulk of work on this should decide. Though if only a few are comfortable using said technology and if they get busy, it may be better to use something others are more familiar with to share the load. My experience using Sequelize is limited and non-existent in TypeORM.

If we just need a final decision on this going forward, I say let's use Sequelize. I created a makeshift poll in Discord if we're still uneasy picking one of the two (keyboard vs movie camera emoji)

[Zeko369]

We'll be using TypeORM