npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@fwl/database

v0.6.6

Published

Database part of Fewlines Web Libraries

Downloads

2

Readme

FWL Database

Disclaimer: this package is made for our internal usage and is only open source for convenience so we might not consider Pull Requests or Issues. Feel free to fork though.

This is part of the Fewlines Web Libraries packages.

The database query runner provided by this package works in a similar way to the Pool entity from PostgreSQL

Installation

yarn add @fwl/database

Usage

You first need to create a new DatabaseQueryRunner:

import * as database from "@fwl/database";

const databaseQueryRunner: database.DatabaseQueryRunner = database.connect(
  tracer,
  config
);

Tracing is activated by default and requires a tracer to pass to the connect method, if you wish to use this package without tracing enabled you can do so:

import * as database from "@fwl/database";

const databaseQueryRunner: database.DatabaseQueryRunnerWithoutTracing = database.connectWithoutTracing(
  config
);

DatabaseQueryRunner gives you two methods: query and close.

close does not take any argument and return a Promise<void> indicating that the connection has successfully been closed.

query takes a query and a list of values:

databaseQueryRunner.query("SELECT * FROM my_table WHERE id = $1", [id]);

This function follows the same logic as the underlying node-pg package.

transaction takes a callback, and gives it a new DatabaseQueryRunner that will execute its queries inside the transaction.

await databaseQueryRunner.transaction(async (client) => {
  await client.query("INSERT INTO my_table (id, name) VALUES ($1, $2)", [
    "10f9a111-bf5c-4e73-96ac-5de87d962929",
    "in-transaction",
  ]);
});

If you want to get the result of your transaction, you would need to return your query:

const { rows } = await databaseQueryRunner.transaction((client) => {
  return client.query(
    "INSERT INTO my_table (id, name) VALUES ($1, $2) RETURNING id",
    ["10f9a111-bf5c-4e73-96ac-5de87d962929", "in-transaction"]
  );
});

// rows contains [{id: "10f9a111-bf5c-4e73-96ac-5de87d962929"}]

If you need to manually rollback a transaction, you can either use the rollback() function or throw an error:

try {
  await databaseQueryRunner.transaction(async (client) => {
    await client.query("INSERT INTO my_table (id, name) VALUES ($1, $2)", [
      "10f9a111-bf5c-4e73-96ac-5de87d962929",
      "in-transaction",
    ]);
    const result = await callFromAnotherService();
    if (result.error) {
      await client.rollback(); // ⚠️ don't forget to await
    }
  });
} catch (error) {
  // typeof error === TransactionError
  // error.message === "transaction rolled back manually"
}
try {
  await databaseQueryRunner.transaction(async (client) => {
    await client.query("INSERT INTO my_table (id, name) VALUES ($1, $2)", [
      "10f9a111-bf5c-4e73-96ac-5de87d962929",
      "in-transaction",
    ]);
    const result = await callFromAnotherService();
    if (result.error) {
      return Promise.reject(new Error("anotherService failed"));
    }
  });
} catch (error) {
  // typeof error === TransactionError
  // error.message === "anotherService failed"
}

⚠️ To avoid calling several times the ROLLBACK query, you can't make a query to rollback your transaction directly, it would result in an error.

Testing

If you want to test your code without having to TRUNCATE everything between each tests (and be able to run tests concurrently), you can create a connection with database.connectInSandbox(options).

The client will work like the others but every queries will be run inside of a transaction that will be rolled back when the connection is closed:

import * as database from "@fwl/database";

let dbClient: database.DatabaseQueryRunner;

beforeEach(async () => {
  dbClient = await database.connectInSandbox({
    username: `${process.env.DATABASE_SQL_USERNAME}`,
    host: `${process.env.DATABASE_SQL_HOST}`,
    password: `${process.env.DATABASE_SQL_PASSWORD}`,
    database: `${process.env.DATABASE_SQL_DATABASE}`,
    port: parseFloat(`${process.env.DATABASE_SQL_PORT}`),
  });
});

afterEach(async () => {
  await dbClient.close();
});