A node.js javascript client implementing the ADODB protocol on windows.
'use strict';
const ADODB = require('node-adodb');
const connection = ADODB.open('Provider=Microsoft.Jet.OLEDB.4.0;Data Source=node-adodb.mdb;');
// Transaction
connection
.transaction([`INSERT INTO Users(UserId, UserName, UserSex, UserBirthday, UserMarried) VALUES (10, "Tom", "Male", "1981/5/10", 0);`,
`INSERT INTO Users(UserId, UserName, UserSex, UserBirthday, UserMarried) VALUES (11, "Brenda", "Female", "2001/1/11", 0);`,
`INSERT INTO Users(UserId, UserName, UserSex, UserBirthday, UserMarried) VALUES (10, "Bill", "Male", "1991/3/9", 0);`])
.then(data => {
console.log("We will not arrive because a duplicate id is generated. When encountering an error do not insert any record.");
})
.catch(error => {
console.error(error);
});
// Execute
connection
.execute('INSERT INTO Users(UserName, UserSex, UserAge) VALUES ("Newton", "Male", 25)')
.then(data => {
console.log(JSON.stringify(data, null, 2));
})
.catch(error => {
console.error(error);
});
// Execute with scalar
connection
.execute('INSERT INTO Users(UserName, UserSex, UserAge) VALUES ("Newton", "Male", 25)', 'SELECT @@Identity AS id')
.then(data => {
console.log(JSON.stringify(data, null, 2));
})
.catch(error => {
console.error(error);
});
// Query
connection
.query('SELECT * FROM Users')
.then(data => {
console.log(JSON.stringify(data, null, 2));
})
.catch(error => {
console.error(error);
});
// Schema
connection
.schema(20)
.then(schema => {
console.log(JSON.stringify(schema, null, 2));
})
.catch(error => {
console.error(error);
});
'use strict';
const ADODB = require('node-adodb');
const connection = ADODB.open('Provider=Microsoft.Jet.OLEDB.4.0;Data Source=node-adodb.mdb;');
async function query() {
try {
const users = await connection.query('SELECT * FROM Users');
console.log(JSON.stringify(users, null, 2));
} catch (error) {
console.error(error);
}
}
query();
ADODB.open(connection[, x64]): ADODB
Initialization database link parameters.
ADODB.query(sql): Promise
Execute a SQL statement that returns a value.
ADODB.execute(sql[, scalar]): Promise
Execute a SQL statement with no return value or with updated statistics.
ADODB.transaction(sql[]): Promise
Execute multiple SQL statement as a transaction.
ADODB.schema(type[, criteria][, id]): Promise
Query database schema information. see: OpenSchema
Set env
DEBUG=ADODB
, see: debug
This library theory supports all databases on the Windows platform that support ADODB connections, and only need to change the database connection string to achieve the operation!
Common access connection strings:
- Access 2000-2003 (*.mdb):
Provider=Microsoft.Jet.OLEDB.4.0;Data Source=node-adodb.mdb;
- Access > 2007 (*.accdb):
Provider=Microsoft.ACE.OLEDB.12.0;Data Source=adodb.accdb;Persist Security Info=False;
orProvider=Microsoft.ACE.OLEDB.15.0;Data Source=adodb.accdb;Persist Security Info=False;
The library need system support
Microsoft.Jet.OLEDB.4.0
orMicrosoft.ACE.OLEDB.12.0
,Windows XP SP2
above supportMicrosoft.Jet.OLEDB.4.0
by default, Others need to install support!Recommended use
Microsoft.ACE.OLEDB.12.0
, download: Microsoft.ACE.OLEDB.12.0
If you want to use this module in an electron app running from an asar package you'll need to make some changes.
- Move
adodb.js
outside the asar package (in this example I use electron-builder, theextraResources
option can move the file outside the asar package)
"extraResources": [
{
"from": "./node_modules/node-adodb/lib/adodb.js",
"to": "adodb.js"
}
]
- Tell the module where to find
adodb.js
while running from an asar package (I added this in electron'smain.js
file)
// Are we running from inside an asar package ?
if (process.mainModule.filename.indexOf('app.asar') !== -1) {
// In that case we need to set the correct path to adodb.js
ADODB.PATH = './resources/adodb.js';
}