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

supple-sql

v0.5.2

Published

[![validate](https://github.com/vampirical/supple-sql/actions/workflows/validate.yml/badge.svg)](https://github.com/vampirical/supple-sql/actions/workflows/validate.yml) [![codecov](https://codecov.io/gh/vampirical/supple-sql/graph/badge.svg?token=R6DEXGF

Downloads

24

Readme

Supple SQL

validate codecov

Minimal viable PostgreSQL only ORM, does as little as it can get away with.

Import

Everything is access through a single top level default export. We call it SQL internally and in examples, you can call it whatever you like.

const SQL = require('supple-sql');

or

import SQL from 'supple-sql';

Connection Management

Connection management defaults to sourcing from a single pool that you provide. If you explicitly pass connections or pools to everything you don't need to specify a default pool.

const pool = new PG.Pool({connectionString, ...});

SQL.setDefaultPool(pool);

If you'd like to run multiple queries on a single connection there's a helper for that.

const result = await SQL.connected(async function (conn) {
  // Pass conn explicitly as the first argument to all your Supple object constructors.
  // Whatever you return will be passed through as the return of connected().
  // If an error occurs either in your code or within your database the connection will be released
  // and either returned to the pool or destroyed if it isn't recoverable.
});

Transactions are managed similarly.

const result = await SQL.transaction(async function (conn) {
  // Same as connected() except the transaction BEGIN/COMMIT/ROLLBACK is also managed.
}, {});

Records

The types that define objects based on tables are called Records. There's a generator to create them from existing tables but they're also pretty easy to write by hand.

class User extends SQL.Record {
  static fields = {
    id: {type: SQL.type.serial, primaryKey: true},
    email: {type: SQL.type.text, nullable: false, unique: true},
    displayName: {type: SQL.type.text, nullable: false, name: 'custom_db_name_display_name'},
    password: {type: SQL.type.text},
    createdAt: {type: SQL.type.timestamptz, nullable: false, defaultValue: SQL.valueNow},
  };
  static primaryKeyFields = ['id'];
  static privateFields = ['password']; // Optional helper for avoiding accidentally serializing sensitive values.
  static table = 'users';
}

Insert a row. These are equivalent.

const user = new User({email: '[email protected]', displayName: 'Test'});
await user.save();

const user = new User();
user.email = '[email protected]';
user.displayName = 'Test';
await user.save();

Find a row.

const user = await User.findByPk(1);
// If not found, user is null.

const user = await User.findOne({email: '[email protected]'});
// If not found, user is null.

const user = new User();
user.email = '[email protected]';
await user.load();
// If not found, load returns false and user.isLoaded = false.

const user = new User({email: '[email protected]'});
await user.load();
// If not found, load returns false and user.isLoaded = false.

const user = new User();
await user.load({email: '[email protected]'});
// If not found, load returns false, user.isLoaded = false, and email isn't set on user.

Update as needed.

const user = await User.findOne({email: '[email protected]'});
user.displayName = 'Max Power';
await user.save(); // Returns true since there was an update made. Only updates the displayName field, does not push unchanged values back to the db.
await user.save(); // Returns false since there was nothing to do.

There are various ways to get data out of records.

// Property access.
console.debug(user.id);
// 1

// Default JSON serialization.
console.debug(JSON.stringify(user));
// {"id": 1, "email": "[email protected]", ...}

// Extract a vanilla object with options.
console.debug(user.data({includeDefaults = false, includePrivate = false, onlyDirty = false, onlySet = false} = {}));
// {id: 1, email: '[email protected]', ...}

Find and Queries

const rows = await User.find({email: SQL.like('%@example.com')}, {orderBy: 'email'});
for (const record of rows) {
  // Find returns a vanilla array of loaded record instances.
}

const stream = await User.find({email: SQL.like('%@example.com')}, {orderBy: 'email', stream: true});
for await (const record of stream) {
  // You can also async iterate through a database cursor for large sets you don't want to keep in memory.  
}

// Find is just a small wrapper on top of creating a query and running it.
const userQuery = User.query({email: SQL.like('%@example.com')}, {orderBy: 'email'});
await userQuery.run();
// userQuery:
//   Is directly iterable for the same rows you'd get out of a non-stream find, and implements all array prototype methods.
//   Has a vanilla javascript array .rows property. 
//   Is async iteratable if stream=true.

Where conditions can be quite complex and deeply nested.

// These are all the same.
await User.find({id: 1, displayName: 'Max Power'}); // An object of values is an implicit AND.
await User.find([{id: 1}, {displayName: 'Max Power'}]); // A top level array is an implicit AND.
await User.find(SQL.and({id: 1}, {displayName: 'Max Power'})); // SQL.and() is an explicit AND.

// Complex comparisons are available.
await User.find({displayName: SQL.ilike('% power')});
await User.find({id: SQL.lessEqual(5)});

// ANDs and ORs can appear as both top level wheres and as values under field keys, nested as deeply as you'd like.
await User.find(SQL.or({id: 1}, {id: 2}));
await User.find({id: SQL.or(1, 2)});

// You can use sub-queries.
await User.find({
  id: SQL.and(
    User.query({displayName: SQL.notEqual('Max Power')}, {returns: 'id'}),
    SQL.greaterThan(10)
  )
});

There are a few things you can't do.

// You can't nest sub-queries inside of value arrays.
// It isn't worth the performance hit necessary to check for them
// and you can just wrap the query and the values using an AND.
SQL.any([User.query({id: 1}, {returns: 'id'}), 100])

// You can't nest field keys under another field key.
// Even in this best case, it is silly, in the worst case it is nonsense.
await User.find({
  id: SQL.and(
    {id: 1},
    {id: 2}
  )
});

Escape Hatches

If you need a bit of raw SQL somewhere, there's new SQL.Value().

const user = User.find({createdAt: SQL.greaterThan(new SQL.Value("now() - '1 day'::interval"))});

If you need to load records manually.

await SQL.connected(async function (conn) {
  const dbResp = await conn.query(COMPLICATED_QUERY);
  const users = dbResp.rows.map(r => User.newFromDbRow(r));
});

TL;DR

const pool = new PG.Pool({connectionString});
SQL.setDefaultPool(pool);

const userInvoices = await SQL.connected(async function (conn) {
  const invoice = await Invoice.findOne(conn, {id: 5});
  if (!invoice) {
    throw new Error('Invoice not found!');
  }
  invoice.total += 1.50;
  await invoice.save();

  return Invoice.find(conn, {userId: invoice.userId}, {orderBy: ['updatedAt', SQL.sort.desc]});
});

Generated JSDoc are included in published packages and the tests serve as additional examples.