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

prisma-datasources

v1.2.1

Published

Implementing a multi datasources use for prisma orm

Downloads

3

Readme

Prisma datasources

Using the library:

To execute the library you should create your prisma like schema and run:

  npx prisma generate

Environment

The connection string should have a tag to say what connection it is and use a '=' to link to the mysql uri, when you need to pass other uri it will be necessary to separate with a blank space. The blank space should be only between the connections strings.

  MYSQL_DATABASES=ds1=mysql://user:pass@host1/db ds2=mysql://user:pass@host2/db

Code

  const Conn = require('prisma_datasources')

  const connections = await Conn.startConnections(process.env.MYSQL_DATABASES)

  await connections.ds1.test.create({ data: {name: 'picle' } })
  await connections.ds2.test.create({ data: {name: 'rick' } })

Since you pass the connections to the startConnections, all your connections will be opened at the same point of the code and will use the same schema you created. In this case all connections should have the same database architecture to use the library.

  const connections = {
    ds1: <datasource1 connection>,
    ds2: <datasource2 connection>
  }