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

volantsyncer

v0.2.1

Published

A KnexJS based DB syncer

Downloads

1

Readme

VolantSyncer - A tiny utility for PrimaryDB to Secondary DB Syncer

VolantSyncer is based on Knex.js - which is a libaray for building a SQL query for Postgres, MSSQL, MySQL, MariaDB, SQLite3, Oracle, and Amazon Redshift.

VolantSyncer is made for migrating data from multiple types of databases, say for example MSSQL to MySQL.

VolantSyncer works by adding a schema definition and selecting keys to import. You just have provide Volant with Source and Destination DB Handles, the table to sync and mapping of columns.

VolantSyncer checks for DB records to be inserted and DB records to be deleted.

It does not modify the Origin server in anyway. It modifies only the destination DB Server :)

Installation

$ npm install volantsyncer --save

Create a small file called sync_users.js with the following contents

var knex = require('knex');
var VolantSyncer = require('volantsyncer');

var config = {};

var knex = require('knex');
config.destination_db = knex({
  client: 'mysql2',
  connection: {
    host : '127.0.0.1',
    user : 'username',
    password : 'password',
    database : 'database_name'
  }
});

config.origin_db = knex({
  client: 'mssql',
  connection: {
    host : 'localhost',
    user : 'SA',
    password : 'password',
    database : 'database'
  }
});

var options = {
  origin_db_handle:config.origin_db,
  origin_table:'Tbl_Users',
  origin_key:'User_id', //primary key

  destination_db_handle:config.destination_db,
  destination_table:'users',
  destination_key:'id', // primary key
  selection:[
    'User_id as id',
    'Email as email',
    'Password_hash as password_hash'
  ],
  dry_run:false // set it to true to just get the stats
};

var action = VolantSyncer.run(options);

console.log('Script is running...');

action.then((result)=>{
  console.log('script finished');
  console.table(result);
  process.exit();
});

Next exectute it like follows:

$ node sync_users.js

The result is something like this

Script is running...
script finished

┌──────────────────────┬────────┐
│       (index)        │ Values │
├──────────────────────┼────────┤
│   origin_elements    │ 49172  │
│ destination_elements │ 49000  │
│  elements_to_delete  │   4    │
│  elements_to_import  │  176   │
│   elements_deleted   │   4    │
│  elements_imported   │  176   │
└──────────────────────┴────────┘

The elements were imported as well as removed to match the elements that were in the origin database.

If you run the script again, you would see:

┌──────────────────────┬────────┐
│       (index)        │ Values │
├──────────────────────┼────────┤
│   origin_elements    │ 49172  │
│ destination_elements │ 49172  │
│  elements_to_delete  │   0    │
│  elements_to_import  │   0    │
│   elements_deleted   │   0    │
│  elements_imported   │   0    │
└──────────────────────┴────────┘