Objection.js VS knex-types

Objection.js is a SQL-friendly ORM for Node.js that supports various relational databases, including PostgreSQL, MySQL, and SQLite. It provides a flexible and expressive query builder. Objection.js is known for its expressive syntax, allowing developers to build complex queries easily. It supports eager loading, transactions, and migrations.

I don't think there's a best per say, but we did recently use Objection on our project. Did the job well, only issue is there's no constructor for the DB Models but it's just something you work around (https://vincit.github.io/objection.js/)

If you aren't using TypeScript I'd very much recommend Objection.js, I've used it multiple times and no complaints so far. You can pass raw SQL queries to it as well so I'm sure it would be a good fit for your project!

I'd also like to point out objection js is no longer actively maintained. I'm going to switch my work's codebase from it eventually because of it.

You should look into Objection.js. IMHO using that will make your life much easier as it seems you are trying to reimplement it's features in this sample code.

Next, let’s set up the database for our newly created Nest application. I’ll be using PostgreSQL, but you can use any of the databases Knex supports. To interact with our database, we’ll be using Objection.js, which is an ORM for Node.js built on top Knex. For this tutorial, we’ll be using Nest Objection, a Nest module for Objection.

GraphQL.js + Knex.js + knex-types (TypeScript generator for Knex)

And in order to have auto-complete and type checking, you can combine it with knex-types.

I generate TypeScript enums and types from the actual database schema using knex-types as part of the yarn db:reset script that used during local development (after making changes to the db schema migration files). See example project.

I tried to take advantage of TypeORM in a couple of projects, but then reverted back to knex + knex-types — just a PostgreSQL client with query builder works great, IMO, especially for GraphQL API development.

Nope. Just plain GraphQL.js + Knex.js (example), often typed manually since it's not where most of the time spend on when building an API server (though it can be automated via a scaffolding script if there are too many db tables). Generating TypeScript definitions off the actual db schema using knex-types (example).

Luckily, there is a solution! Assuming you have a database table that looks like this (Knex migration):