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 🙏

© 2025 – Pkg Stats / Ryan Hefner

loopback-connector-postgresql-hc

v1.0.0

Published

Loopback PostgreSQL Connector

Downloads

8

Readme

loopback-connector-postgresql

The PostgreSQL Connector module for for loopback-datasource-juggler.

Please see the official documentation.

Connector settings

The connector can be configured using the following settings from the data source.

  • url: The URL to the database, such as 'postgres://test:mypassword@localhost:5432/dev'
  • host or hostname (default to 'localhost'): The host name or ip address of the PostgreSQL DB server
  • port (default to 5432): The port number of the PostgreSQL DB server
  • username or user: The user name to connect to the PostgreSQL DB
  • password: The password
  • database: The PostgreSQL database name
  • debug (default to false)

NOTE: By default, the 'public' schema is used for all tables.

The PostgreSQL connector uses node-postgres as the driver. See more information about configuration parameters, check https://github.com/brianc/node-postgres/wiki/Client#constructors.

Discovering Models

PostgreSQL data sources allow you to discover model definition information from existing postgresql databases. See the following APIs:

Model definition for PostgreSQL

The model definition consists of the following properties:

  • name: Name of the model, by default, it's the camel case of the table
  • options: Model level operations and mapping to PostgreSQL schema/table
  • properties: Property definitions, including mapping to PostgreSQL column

    {"name": "Inventory", "options": {
      "idInjection": false,
      "postgresql": {
        "schema": "strongloop",
        "table": "inventory"
      }
    }, "properties": {
      "id": {
        "type": "String",
        "required": false,
        "length": 64,
        "precision": null,
        "scale": null,
        "postgresql": {
          "columnName": "id",
          "dataType": "character varying",
          "dataLength": 64,
          "dataPrecision": null,
          "dataScale": null,
          "nullable": "NO"
        }
      },
      "productId": {
        "type": "String",
        "required": false,
        "length": 20,
        "precision": null,
        "scale": null,
        "id": 1,
        "postgresql": {
          "columnName": "product_id",
          "dataType": "character varying",
          "dataLength": 20,
          "dataPrecision": null,
          "dataScale": null,
          "nullable": "YES"
        }
      },
      "locationId": {
        "type": "String",
        "required": false,
        "length": 20,
        "precision": null,
        "scale": null,
        "id": 1,
        "postgresql": {
          "columnName": "location_id",
          "dataType": "character varying",
          "dataLength": 20,
          "dataPrecision": null,
          "dataScale": null,
          "nullable": "YES"
        }
      },
      "available": {
        "type": "Number",
        "required": false,
        "length": null,
        "precision": 32,
        "scale": 0,
        "postgresql": {
          "columnName": "available",
          "dataType": "integer",
          "dataLength": null,
          "dataPrecision": 32,
          "dataScale": 0,
          "nullable": "YES"
        }
      },
      "total": {
        "type": "Number",
        "required": false,
        "length": null,
        "precision": 32,
        "scale": 0,
        "postgresql": {
          "columnName": "total",
          "dataType": "integer",
          "dataLength": null,
          "dataPrecision": 32,
          "dataScale": 0,
          "nullable": "YES"
        }
      }
    }}

Type Mapping

  • Number
  • Boolean
  • String
  • Object
  • Date
  • Array
  • Buffer

JSON to PostgreSQL Types

  • String|JSON|Text|default: VARCHAR, default length is 1024
  • Number: INTEGER
  • Date: TIMESTAMP WITH TIME ZONE
  • Timestamp: TIMESTAMP WITH TIME ZONE
  • Boolean: BOOLEAN

PostgreSQL Types to JSON

  • BOOLEAN: Boolean
  • VARCHAR|CHARACTER VARYING|CHARACTER|CHAR|TEXT: String
  • BYTEA: Binary;
  • SMALLINT|INTEGER|BIGINT|DECIMAL|NUMERIC|REAL|DOUBLE|SERIAL|BIGSERIAL: Number
  • DATE|TIMESTAMP|TIME: Date
  • POINT: GeoPoint

Destroying Models

Destroying models may result in errors due to foreign key integrity. Make sure to delete any related models first before calling delete on model's with relationships.

Auto Migrate / Auto Update

After making changes to your model properties you must call Model.automigrate() or Model.autoupdate(). Only call Model.automigrate() on new models as it will drop existing tables.

LoopBack PostgreSQL connector creates the following schema objects for a given model:

  • A table, for example, PRODUCT under the 'public' schema within the database

Running tests

The tests in this repository are mainly integration tests, meaning you will need to run them using our preconfigured test server.

  1. Ask a core developer for instructions on how to set up test server credentials on your machine
  2. npm test