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

@debugr/sql-common

v3.0.0-rc.6

Published

Common interfaces and utility functions for SQL plugins

Downloads

111

Readme

Common SQL interfaces and utilities

This package defines the shape of the data included in entries which represent an SQL query. Plugins which produce or consume such entries should conform to this shape. Unless you're developing a Debugr plugin or log handler, you usually don't need to worry about this package, as it will be installed and used automatically when required.

For plugin developers

The package exports the following type definitions:

export interface SqlQueryData {
  query: string;         // The SQL query
  parameters?: any[];    // Any parameters passed to the SQL query
  error?: string;        // Any error message produced by the query
  stack?: string;        // Stack trace for the call which issued a query
  affectedRows?: number; // The number of rows affected by a DML query
  rows?: number;         // The number of rows selected by a DQL query
  time?: number;         // The time the query took to execute
}

export interface SqlQueryLogEntry<
  TTaskContext extends TContextBase = TContextBase,
  TGlobalContext extends TContextShape = TContextShape,
  > extends LogEntry<TTaskContext, TGlobalContext> {
  type: 'sql.query';
  data: SqlQueryData;
}

There are also a couple of utility functions exported:

  • formatQueryTime(ms: number, html: boolean = false): string - This function formats the duration of an SQL query as a fraction of seconds if the duration was over 1000ms, or as milliseconds if the duration was lower, with the numeric part optionally wrapped in a HTML <strong> tag when html is set to true. For example: 35.753241 would result in 35.75 ms or <strong>35.75</strong> ms and 5645.6768576 would result in 5.64 s or <strong>5.64</strong> s.
  • createQueryFormatter(): (query: string) => string - This function attempts to load the @sqltools/formatter package and returns a preconfigured callback which converts reserved words to uppercase and inserts some strategic newlines to make the query easier to read; if the package isn't installed, it simply returns a noop callback which just returns the passed query as-is.