tedious VS TypeORM

SQL Server does not support IAM database authentication, so we can only use built-in password authentication. Notice that we also have to pass a dummy server property when creating a connection pool. This is due to a bug in the tedious driver, which always requires the server property, even though it is not used when a custom connection builder is provided.

A quick search gave me these: https://learn.microsoft.com/en-us/sql/connect/node-js/node-js-driver-for-sql-server?view=sql-server-ver16 or https://github.com/tediousjs/tedious

Node TDS module for connecting to SQL Server databases. Tedious is a pure-Javascript implementation of the TDS protocol, which is used to interact with instances of Microsoft's SQL Server. [TEDIOUSJS]

In my project I also use TypeORM with plugin for NestJS. To do this I needed to add custom options for esbuild. I implemented a feature similar to custom-esbuild to allow users to add their own plugins to the build.

TypeORM will be the ORM to interact with our PostgreSQL database. An ORM stands for Object-Relational Mapping and is used to interact with relational databases like MySQL, PostgreSQL, or Oracle. Also, we need TypeORM-Nestjs integration. Run the command below to install it.

Let’s walk through an example where we integrate with an SQLite database using TypeORM.

// src/main/database/dataSource.ts import path from "node:path"; import "reflect-metadata"; import { DataSource } from "typeorm"; import { UserEntity } from "./entities/user/user.entity"; import { PostEntity } from "./entities/post/post.entity"; const isElectron = !!process.versions.electron; # simple trick to see if the data source is called from the Electron app or CLI (for migrations scripts) const isProduction = process.env.NODE_ENV === "production"; let databasePath: string; if (isElectron) { // eslint-disable-next-line @typescript-eslint/no-require-imports const { app } = require("electron"); databasePath = path.join( app.getPath("userData"), app.isPackaged ? "app-name.sqlite" : "app-name.dev.sqlite" ); } else { // use hardcoded path for running migrations in development (macOS) databasePath = path.join( "/Users/user/Library/Application Support/app-name/", isProduction ? "app-name.sqlite" : "app-name.dev.sqlite" ); } // https://typeorm.io/data-source-options#better-sqlite3-data-source-options const dataSource = new DataSource({ type: "better-sqlite3", database: databasePath, entities: [UserEntity, PostEntity], migrations: [ path.join(__dirname, isElectron ? "database" : "", "/migrations/*.{js,ts}"), ], synchronize: false, # important logging: true # use this for debugging }); export const entityManager = dataSource.createEntityManager(); export default dataSource;

For relational databases, there are many different libraries you can use here, but if you use an SQL database, you can consider TypeORM.

2. TypeORM

Using TypeORM in Node.js application gives you nice support of Typescript for ORM models. Lets see how can we setup PostgreSQL and tsvector with TypeORM

For example, the increasingly popular Prisma has high type safety but adopts the Table Gateway pattern. The closest fit was TypeORM, which uses the Active Record pattern, but its type support is weaker compared to recent ORMs, and its release frequency has been low recently.

If you use Sequalize, TypeORM or for MongoDB, we have Mongoose these types of ORM tools, then you are safe by default because these help us against the SQL query injection attacks by default.