🔧✨ Safely create & execute parameterized SQL queries using tagged template strings.

const [user] = await sql`SELECT * FROM users WHERE id = ${userId}`;

This runs the following query:

SELECT * FROM users WHERE id = ?
-- with parameters: [123]

Features:

Automatically parameterizes values and escapes identifiers (e.g. table or column names)
Supports nested & concatenated SQL expressions
Provides a handful of utilities for creating common SQL expressions such as AND/OR lists, field IN (...), and updates/inserts.
Supports promises and cursors for efficient memory usage
Includes full TypeScript support (including generic types for query results)
Supports any database driver (includes built-in drivers for MySQL, PostgreSQL, and SQLite, but you can easily create your own)
100% test coverage
Lightweight (no dependencies)
MIT licensed

Why?

The answer to this depends on the question you are asking:

Why not just use regular strings?

Regular strings might be fine for simple queries, but they don't help you write safe queries. As your queries grow in complexity, it can be difficult to keep track of all the values and identifiers that need to be parameterized or escaped, leaving your queries open to injection vulnerabilities. Additionally, it can be difficult to build larger queries out of smaller pieces using only string concatenation.

SqlTags makes it easy to write safe queries by automatically parameterizing values and escaping identifiers. It also provides utilities for creating common SQL expressions, making it easier to build larger queries out of smaller pieces.

Why not use an ORM or query builder?

ORMs and query builders are great for simple CRUD operations, but they can be a burden for more complex queries. Often, you'll want to debug and optimize complex SQL queries directly in a database console application (such as DataGrip, pgAdmin, etc), and then copy them back into your application code. An ORM makes this difficult because the resulting SQL has to be translated every time you do this.

SQL queries with SqlTags are more transparent, making it less cumbersome to move it between your application and database console when needed.

Why not use [insert existing library name here]?

There are a number of existing libraries that provide similar functionality to SqlTags. I created SqlTags because they all lacked some key feature or had a less-than-ideal API. Here are some comparisons with other popular libraries:

Postgres https://www.npmjs.com/package/postgres
- This excellent library was the main inspiration for SqlTags, but it only supports Postgres.
- Personally, I found it confusing to have so many different ways to call the sql() function. SqlTags is more explicit with the features, using separate methods such as sql.id(), sql.join(), etc.
SQL Template Strings https://npmjs.com/package/sql-template-strings
SQL Tag https://npmjs.com/package/sql-tag
SQL Template Tag https://npmjs.com/package/sql-template-tag
pg-template-tag https://www.npmjs.com/package/pg-template-tag
- All these options have a more verbose API/syntax, requiring you to pass the result of the tag to a database driver function to execute the query.
- Few or no utilities for building common SQL expressions or escaping identifiers.
- Only support a small, fixed set of database flavors.
- sql-tag doesn't support TypeScript.

Installation

Choose the driver for your database flavor:

npm install @sqltags/pg
npm install @sqltags/mysql
npm install @sqltags/sqlite
Or create your own with npm install @sqltags/core

Then, create a template tag using the factory function from your chosen driver library.

Here's an example using MySQL (there are other drivers for PostgreSQL and SQLite, or you can create your own):

import { createMySqlTag } from '@sqltags/mysql';
import mysql from 'mysql2';

// Create your connection object, e.g.:
const client = mysql.createConnection({
  /* ... */
});

// Then create the sql tag using your connection:
const sql = createMySqlTag(client);

For documentation on the driver-specific setup, check out their readme pages:

MySQL
PostgreSQL
SQLite

Querying

To execute a query, simply use the tag with a SQL query, and await the result:

const users = await sql<User>`SELECT * FROM users`;

The result is an array containing the query results. The array also has an additional property info, which has additional information about the query that the driver provides (e.g. the column information, or number of affected rows, etc; this value is defined by the underlying database driver).

Cursors

To reduce memory usage, it is possible to execute a query and fetch rows one at a time (instead of all at once) using a cursor. To get a cursor, use the .cursor() method on a tagged query string. This returns an AsyncIterable that can be iterated using a for await ... of loop.

// Note that this line is not awaited! The cursor is not executed until it is iterated.
const cursor = sql<User>`SELECT * FROM users`.cursor();

for await (const user of cursor) {
  // ...
}

.cursor() also accepts a configuration object, which is defined by and passed directly to the driver.

TypeScript

You can specify the return type of each row by passing a generic type argument to the SQL tag:

interface User {
  id: number;
  name: string;
  email: string;
  // etc.
}

const users = await sql<User>`SELECT * FROM users`;

users will be of type User[], with an additional property users.info which contains additional query execution information (the type is defined by the driver).

Building SQL queries

Parameterizing values

Values will automatically be parameterized when they are interpolated into the query template string.

const users = await sql`SELECT * FROM users WHERE id = ${userId}`;

"Parameterized" means that they are replaced by a placeholder (e.g. ? or $1) and passed to the database driver separately from the query string. This is the safest way to execute queries, and prevents SQL injection attacks.

Warning! Be careful when interpolating undefined values. They will be omitted from the query entirely, potentially resulting in an invalid query:
const userId = undefined;
const users = await sql`SELECT * FROM users WHERE id = ${userId}`;
// Executes an invalid statement:
// `SELECT * FROM users WHERE id = `
// with no query parameters!
Other "falsy" values (e.g. null, "", false, 0) will be included and sent as query parameters.

Escaping identifiers

sql.id(identifier: string): string

To safely embed an escaped identifier (e.g. a table or column name) into a query string, use the tag's .id() method:

const table = 'users';
const users = await sql`SELECT * FROM ${sql.id(table)}`;

Identifiers are escaped appropriately by the driver, but are not parameterized.

Nested SQL expressions

To nest SQL expressions, just embed a sql tag expression:

const users = await sql`
  SELECT *
  FROM users
  ${userId ? sql`WHERE id = ${userId}` : undefined}
`;

Remember that embedding plain strings without the sql tag will escape/parameterize them.

sql.raw(value: string)

To embed variables directly without parameterizing them, use the tag's .raw() method:

const whereClause = "status = 'active'";
const users = await sql`
  SELECT *
  FROM users
  where ${sql.raw(whereClause)}
`;

Concatenating SQL expressions

Because the return value of a SQL tag is not a string, you cannot concatenate them using the + operator.

const query = sql`SELECT * FROM users`;

if (userId) {
  // ❌ This will NOT work!
  query += sql` WHERE id = ${userId}`;
}

Instead, try building queries using embedded expressions:

const query = sql`
  SELECT *
  FROM users
  ${userId ? sql`WHERE id = ${userId}` : undefined}
`;

Another approach is to push query parts onto an array, and join them using the tag's .join('') method:

const queryParts = [sql`SELECT * FROM users`];

if (userId) {
  queryParts.push(sql`WHERE id = ${userId}`);
}

// Join the query parts, separating each with a newline:
const query = sql.join(queryParts, '\n');

const users = await query;

SQL expression helpers

The SQL tag object also provides a handful of helper methods to construct common SQL expressions.

All expression helper methods generally accept both raw values and other nested tagged SQL expressions.

AND and OR expressions

sql.and(values: any[])
sql.or(values: any[])

Joins an array of expressions using AND and OR, grouped inside parentheses. They can be nested, and will be grouped in parentheses appropriately. undefined values are omitted, but be careful with other falsy values (e.g. null, false, 0).

const users = await sql`
  SELECT *
  FROM users
  WHERE ${sql.and(
    userId ? sql`id = ${userId}` : undefined,
    sql.or(
      sql`status = 'active'`,
      sql`status = 'pending'`,
      // ...
    ),
  )}
`;

// SELECT *
// FROM users
// WHERE (id = ? AND (status = ? OR status = ?))
// with parameters: [123, 'active', 'pending']

UPDATE expressions

sql.setValues(value: Record<string, any>, pickFrom?: string[])

Generates a list of `column` = 'value' pairs for use in an UPDATE SET statement. You can optionally include a list of properties to pick from the object.

const user = {
  id: 1,
  name: 'Alex',
  email: 'test@example.com',
  status: 'active',
};

// Updates only the `name` and `status` columns:
await sql`
  UPDATE users
  SET ${sql.setValues(user, 'name', 'status')}
  WHERE id = ${user.id}
`;

// UPDATE users
// SET name = ?, status = ?
// WHERE id = ?
// with parameters: ['Alex', 'active', 1]

INSERT expressions

sql.insertValues(values: any[], pickFrom?: string[])

Generates a (`columnA`, `columnB`) VALUES (value1, value2), (value3, value4) type of expression for use in an INSERT statement.

const newUsers = [
  { name: 'Alex', email: 'alex@example.com' },
  { name: 'Bob', email: 'bob@example.com' },
];

// Inserts ALL properties from objects in `newUsers`:
await sql`INSERT INTO users ${sql.insertValues(newUsers)}`;

// INSERT INTO users (`name`, `email`) VALUES (?, ?), (?, ?)
// with parameters: ['Alex', 'alex@example', 'Bob', 'bob@example']

Just like .setValues(), You can optionally include a list of properties to pick from each object.

IN expressions

sql.in(values: any[])

To generate an expression like `column` IN (value1, value2, etc), use the tag's .in() method:

const users = await sql`SELECT * FROM users WHERE ${sql.in('id', [1, 2, 3])}`;

// SELECT * FROM users WHERE `id` IN (?, ?, ?)
// with parameters: [1, 2, 3]

Joining/concatenating values

sql.join(values: any[], joinWith: string = ', ')

To join (concatenate) an array of values or expressions, use the tag's .join() method:

const ids = [1, 2, 3];
const users = await sql`SELECT * FROM users WHERE id IN (${sql.join(ids)})`;

// SELECT * FROM users WHERE id IN (?, ?, ?)
// with parameters: [1, 2, 3]

Values will be joined with a comma by default, but you can pass a specific separator as the second argument:

const users = await sql`
  SELECT * FROM users 
  WHERE ${sql.join(
    [
      // Better to use `sql.and()` for this, but just for example:
      sql`id = ${userId}`,
      sql`status = 'active'`,
    ],
    ' AND ',
  )}
`;

// SELECT * FROM users WHERE id = ? AND status = ?
// with parameters: [123, 'active']

Query Events

The SqlTag class extends EventEmitter and provides a strongly-typed interface for handling database query events. This allows you to attach listeners to specific events emitted during the query lifecycle. For example:

sql.on('afterQuery', (event) => {
  // ...
});

Here are the events you can listen to:

`'beforeQuery'`

Emitted immediately before a query is executed. Use this event to inspect or log the query before it runs.

The event object has the following properties:

queryText - The query string.
params - The query parameters.

`'afterQuery'`

Emitted after a query is executed and the result is received. Use this event to inspect or log the query result and performance.

The event object has the following properties:

queryText - The query string.
params - The query parameters.
result - The query result.
info - Additional information about the query (e.g. column definitions, rows affected, etc). This is provided by the database driver.
ms - The query execution time in milliseconds.

Note that this event is not emitted for cursors.

Creating SqlTags for other database clients

A SqlTag instance is just a thin wrapper around a database client driver. Any database client library that supports parameterized queries can be used with SqlTags.

To support a database client, you just need to create an object that implements the SqlTagDriver interface, and pass it to the SqlTag constructor:

import { SqlTag, type SqlTagDriver } from '@sqltags/core';

const driver: SqlTagDriver = {
  // ... implement the interface methods here ...
};

const sql = new SqlTag(driver);

The SqlTagDriver interface defines the methods that a SqlTag instance needs to parameterize values, run queries, etc. It is defined and documented here, and you can see example implementations for MySQL, PostgreSQL, and SQLite.

As the existing driver implementations demonstrate, the convention is to create a "factory" function that accepts a database connection object, and returns a new instance of the SqlTag class using the custom driver:

import { SqlTag } from '@sqltags/core';

function createDriver(client: SomeDbClient): SqlTagDriver {
  return {
    // ... implement the interface methods here ...
  };
}

export function createSqlTag(client: SomeDbClient) {
  return new SqlTag(createDriver(client));
}

// Then use the function to create an instance of your SqlTag class:
const sql = createSqlTag(someClient);

The SqlTag instance must also define the TypeScript types for the query metadata (such as rows updated/inserted, column definitions, etc), and the cursor options parameter.

Here is an example implementation for an imaginary database driver called "CoolDb". The purpose of each implemented method is further described in the SqlTagDriver interface definition.

import { SqlTag, SqlTagDriver } from '@sqltags/core';

// Imaginary database client library:
import {
  type CoolDbConnection,
  type CoolQueryInfo,
  type CoolCursorOptions,
} from 'cool-database-library';

// The driver implementation:
function createDriver(client: CoolDbConnection): SqlTagDriver<
  // Type parameters specify the type of the query metadata and cursor options:
  CoolQueryInfo,
  CoolCursorOptions
> {
  return {
    // Parameterize a value by replacing it with the placeholder appropriate for your database:
    parameterizeValue(value: any, paramIndex: number): string {
      return `$${paramIndex}`; // $1, $2, $3, etc.
    },

    // Escape an identifier by replacing it with the appropriate string:
    escapeIdentifier(identifier: string): string {
      return `"${identifier.replaceAll('"', '""')}"`; // e.g. "my_terrible""_table_name"
    },

    // Execute a query and return the results and metadata:
    async query(sql: string, params: any[]): Promise<[any[], CoolQueryInfo]> {
      // Use the `client` object passed to the function to execute the query:
      const res = await client.query(sql, params);
      // For this example, res.rows contains the array of row objects, and
      // res.info is a "CoolQueryInfo" object.
      return [res.rows, res.info];
    },

    // Execute a query with a cursor and return an async iterable:
    async *cursor(sql: string, params: any[], options: CoolCursorOptions): AsyncIterable<any> {
      // ... (cursor implementation can be complex; see existing drivers for examples)
    },
  };
}

// The factory method that returns the SqlTag instance:
export function createCoolDbTag(client: CoolDbConnection) {
  return new SqlTag(createDriver(client));
}

Then you can use the factory method to create a SqlTag and start querying:

// Connect to your database using your client library, e.g.:
const db = new CoolDbConnection({
  /* ... */
});

// Use the function you created to create a SqlTag instance:
const sql = createCoolDbTag(db);

// Query!
const users = await sql`SELECT * FROM users WHERE id = ${userId}`;

Contributing

Contributions are welcome! Please open an issue or pull request on the GitHub repository.

SqlTags is written in TypeScript, and uses Jest for testing. To run the tests, clone the repository and run npm install to install the dependencies. Then run npm test to run the tests.

SqlTags supports custom database drivers, and they can be published separately. If you create a driver and want it listed here, please open a pull request with a README modification!

License

MIT License

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

README.md

README.md

Contents

Why?

Why not just use regular strings?

Why not use an ORM or query builder?

Why not use [insert existing library name here]?

Installation

Querying

Cursors

TypeScript

Building SQL queries

Parameterizing values

Escaping identifiers

Nested SQL expressions

Concatenating SQL expressions

SQL expression helpers

AND and OR expressions

UPDATE expressions

INSERT expressions

IN expressions

Joining/concatenating values

Query Events

`'beforeQuery'`

`'afterQuery'`

Creating SqlTags for other database clients

Contributing

License

Files

README.md

Latest commit

History

README.md

File metadata and controls

Contents

Why?

Why not just use regular strings?

Why not use an ORM or query builder?

Why not use [insert existing library name here]?

Installation

Querying

Cursors

TypeScript

Building SQL queries

Parameterizing values

Escaping identifiers

Nested SQL expressions

Concatenating SQL expressions

SQL expression helpers

AND and OR expressions

UPDATE expressions

INSERT expressions

IN expressions

Joining/concatenating values

Query Events

'beforeQuery'

'afterQuery'

Creating SqlTags for other database clients

Contributing

License

`'beforeQuery'`

`'afterQuery'`