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

@jaggr2/sqlanywhere

v2.0.5

Published

Fork of SQL Anywhere JavaScript Driver for Node12/14

Downloads

3

Readme

@jaggr2/node-sqlanywhere

This is a fork of Node.js SAP SQL Anywhere driver (https://github.com/sqlanywhere/node-sqlanywhere), because the original project seems to be unmaintained right now (even the pull requests for latest NodeJS versions are not applied)

USE ON YOUR OWN RISK

Fork Info

This fork was build against NodeJS 14 with SQL Anywhere Driver v16 (64-Bit)

Fork Install

npm install @jaggr2/sqlanywhere

Prerequisites

This driver communicates with the native SQL Anywhere libraries, and thus requires native compilation. Native compilation is managed by node-gyp. Please see that project for additional prerequisites including Python 2.7, and C/C++ tool chain.

Getting Started

var sqlanywhere = require('sqlanywhere');

var conn = sqlanywhere.createConnection();

var conn_params = {
  Server  : 'demo16',
  UserId  : 'DBA',
  Password: 'sql'
};


conn.connect(conn_params, function(err) {
  if (err) throw err;
  conn.exec('SELECT Name, Description FROM Products WHERE id = ?', [301], function (err, result) {
    if (err) throw err;

    console.log('Name: ', result[0].Name, ', Description: ', result[0].Description);
    // output --> Name: Tee Shirt, Description: V-neck
    conn.disconnect();
  })
});

Establish a database connection

Connecting

A database connection object is created by calling createConnection. The connection is established by calling the connection object's connect method, and passing in an object representing connection parameters. The object can contain most valid connection properties.

Example: Connecting over TCP/IP
conn.connect({
  Host    : 'localhost:2638'
  UserId  : 'DBA',
  Password: 'sql'
});
Example: Auto-starting a database on first connection
conn.connect({
  DatabaseFile: 'demo.db',
  AutoStart: 'YES',
  UserId: 'DBA',
  Password: 'sql',
});

Disconnecting

The disconnect() function closes the connection. As of version 1.0.16, you can also use close().

conn.disconnect(function(err) {
  if (err) throw err;
  console.log('Disconnected');
});

Determining whether you are connected

The connected() method was added in version 1.0.16.

var conn = sqlanywhere.createConnection();
var connected = conn.connected(); // connected === false
conn.connect({ ... } );
connected = conn.connected(); // connected === true
conn.disconnect();
connected = conn.connected(); // connected === false

Direct Statement Execution

Direct statement execution is the simplest way to execute SQL statements. The inputs are the SQL command to be executed, and an optional array of positional arguments. The result is returned using callbacks. The type of returned result depends on the kind of statement.

DDL Statement

In the case of a successful DDL Statement nothing is returned.

conn.exec('CREATE TABLE Test (id INTEGER PRIMARY KEY DEFAULT AUTOINCREMENT, msg LONG VARCHAR)', function (err, result) {
  if (err) throw err;
  console.log('Table Test created!');
});

DML Statement

In the case of a DML Statement the number of affectedRows is returned.

conn.exec("INSERT INTO Test(msg) SELECT 'Hello,' || row_num FROM sa_rowgenerator(1, 10)", function (err, affectedRows) {
  if (err) throw err;
  console.log('Number of affected rows:', affectedRows);
  conn.commit();
});

Query

The exec function is a convenient way to completely retrieve the result of a query. In this case all selected rows are fetched and returned in the callback.

conn.exec("SELECT * FROM Test WHERE id < 5", function (err, rows) {
  if (err) throw err;
  console.log('Rows:', rows);
});

Values in the query can be substitued with JavaScript variables by using ? placeholders in the query, and passing an array of positional arguments.

conn.exec("SELECT * FROM Test WHERE id BETWEEN ? AND ?", [5, 8], function (err, rows) {
  if (err) throw err;
  console.log('Rows:', rows);
});

As of version 1.0.16, wide inserts, deletes, and updates are possible by passing in an array of arrays, one per row. For example, the following statement inserts three rows rather than just one:

conn.exec("INSERT INTO Test VALUES ( ?, ? )", [ [1, 10], [2, 20], [3, 30] ], function (err, rows) {
  if (err) throw err;
  console.log('Rows:', rows); // should display 3
});

When using wide statements, each array must have the same number of elements and the type of the values must be the same in each row.

Prepared Statement Execution

Prepare a Statement

The connection returns a statement object which can be executed multiple times.

conn.prepare('SELECT * FROM Test WHERE id = ?', function (err, stmt){
  if (err) throw err;
  // do something with the statement
});

Execute a Statement

The execution of a prepared statement is similar to the direct statement execution. The first parameter of exec function is an array with positional parameters. With version 1.0.16, wide statements (except SELECT) are supported here as well.

stmt.exec([16], function(err, rows) {
  if (err) throw err;
  console.log("Rows: ", rows);
});

Fetching multiple result sets

As of version 1.0.16, you can prepare and execute a batch containing multiple select statements. To do this, you would prepare the multiple select statements and use stmt.exec() to fetch the first result set. To fetch the next result set, call stmt.getMoreResults(). getMoreResults takes an optional callback function (which takes the same arguments as exec), making it asynchronous. The getMoreResults() function returns undefined (or passes it to the callback function) after the last result set.

A simple synchronous example is below.

stmt = conn.prepare( 'select 1 as a from dummy; select 2 as b, 3 as c from dummy' );
rs = stmt.exec();
// rs == [ { a: 1 } ]
rs = stmt.getMoreResults();
// rs = [ { b: 2, c: 3 } ]
stmt.drop();

Drop Statement

stmt.drop(function(err) {
  if (err) throw err;
});

Transaction Handling

Transactions are not automatically commited. Executing a statement implicitly starts a new transaction that must be explicitly committed, or rolled back.

Commit a Transaction

conn.commit(function(err) {
  if (err) throw err;
  console.log('Transaction commited.');
});

Rollback a Transaction

conn.rollback(function(err) {
  if (err) throw err;
  console.log('Transaction rolled back.');
});

Resources