Package Exports
- any-db
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (any-db) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
any-db - a less-opinionated database abstraction layer.
Synopsis
(There's also detailed API documentation available)
var anyDB = require('any-db')
var dbURL = 'driver://user:pass@hostname/database'Establish a connection:
var conn = anyDB.createConnection(dbURL) // Takes an optional callbackMake queries:
var sql = 'SELECT * FROM my_table'
conn.query(sql).on('row', function (row) {}) // evented
conn.query(sql, function (error, result) {}) // or callbackUse bound parameters:
sql += ' WHERE my_column = ?'
conn.query(sql, [42]).on('row', ...) // again, evented
conn.query(sql, [42], function (err, res) {}) // or callbackClose a connection:
conn.end()Start a transaction:
var tx = conn.begin() // Can also take a callback
tx.on('error', function (err) {}) // Emitted for unhandled query errors
tx.query(...) // same interface as connections, plus...
tx.commit() // takes an optional callback for errors
tx.rollback() // this tooCreate a connection pool that maintains 2-20 connections
var pool = anyDB.createPool(dbURL, {min: 2, max: 20})
pool.query(...) // perform a single query, same API as connection
var tx = pool.begin() // start a transaction, again, same API as connection
pool.close() // close the pool (call when your app should exit)Description
The purpose of this library is to provide a consistent API for the commonly used functionality of SQL database drivers, while avoiding altering driver behaviour as much as possible.
The long-term goal of this project is to serve as the testing ground for finding a suitable common interface, then (hopefully) convincing driver implementors to support it natively. In short, any-db hopes to prove it's usefulness well enough that most of it can be obviated by the drivers themselves.
Things it does
- Supports MySQL, Postgres, and SQLite3 as equally as possible. (More driver support is very much welcomed!)
- Parses connection parameters from URLs:
driver://user:pass@host/database - Streams results or gets them all at once, using an api almost identical to the existing interfaces of the MySQL and Postgres drivers.
- A simple, solid, connection pool with the ability to execute queries
directly on a pool for auto-release behaviour. E.g. - this will never leak
connections:
pool.query("SELECT 1", function (err, results) { ... }) - Stateful transaction objects for managing database transactions.
Things it might do (feedback needed!)
- Provide a common result set API.
Things it will never do
- Add it's own query helper methods like
.firstor.fetchAll - Include any sort of SQL string building. You might want to try my other library gesundheit, or one of the many alternatives for that. (send me pull requests to list your libs here)
Install
npm install --save any-db
npm install --save {pg,mysql,sqlite3}Contributing
For ideas that would change an existing API or behaviour please open an issue to propose the change before spending time on implementing it. I know it's hard (I code-first-ask-questions-later way too frequently 😄) but I'd really hate for anybody to put their time into something that won't be merged.
I'm not terribly picky about code-formatting, but please try and keep lines under 80 characters long if you can help it.
License
MIT
