Important
react-native-quick-sqlite has been deprecated in favor of this new Nitro module implementation.
From major version 9.0.0 on, will be shipped in the NPM package react-native-nitro-sqlite. We will still provide bug fixes to [email protected] for the coming weeks/months.
bun add react-native-nitro-sqlite
npx pod-install
Nitro SQLite embeds the latest version of SQLite and provides a low-level JSI-backed API to execute SQL queries.
Performance metrics are intentionally not presented, anecdotic testimonies suggest anywhere between 2x and 5x speed improvement. On small queries you might not notice a difference with the old bridge but as you send large data to JS the speed increase is considerable.
Starting on version 8.0.0 only React-Native 0.71 onwards is supported. This is due to internal changes to React-Native artifacts. If you are on < 0.71 use the latest 7.x.x version.
TypeORM is officially supported, however, there is currently a parsing issue with React-Native 0.71 and its babel configuration and therefore it will not work, nothing wrong with this package, this is purely an issue on TypeORM.
import {open} from 'react-native-nitro-sqlite'
const db = open('myDb.sqlite')
// The db object now contains the following methods:
db = {
close: () => void,
delete: () => void,
attach: (dbNameToAttach: string, alias: string, location?: string) => void,
detach: (alias: string) => void,
transaction: (fn: (tx: Transaction) => void) => Promise<void>,
execute: (query: string, params?: any[]) => QueryResult,
executeAsync: (
query: string,
params?: any[]
) => Promise<QueryResult>,
executeBatch: (commands: SQLBatchParams[]) => BatchQueryResult,
executeBatchAsync: (commands: SQLBatchParams[]) => Promise<BatchQueryResult>,
loadFile: (location: string) => FileLoadResult;,
loadFileAsync: (location: string) => Promise<FileLoadResult>
}The basic query is synchronous, it will block rendering on large operations, further below you will find async versions.
import { open } from 'react-native-nitro-sqlite';
try {
const db = open('myDb.sqlite');
let { rows } = db.execute('SELECT somevalue FROM sometable');
rows.forEach((row) => {
console.log(row);
});
let { rowsAffected } = await db.executeAsync(
'UPDATE sometable SET somecolumn = ? where somekey = ?',
[0, 1]
);
console.log(`Update affected ${rowsAffected} rows`);
} catch (e) {
console.error('Something went wrong executing SQL commands:', e.message);
}Throwing an error inside the callback will ROLLBACK the transaction.
If you want to execute a large set of commands as fast as possible you should use the executeBatch method, it wraps all the commands in a transaction and has less overhead.
await NitroSQLite.transaction('myDatabase', (tx) => {
const { status } = tx.execute(
'UPDATE sometable SET somecolumn = ? where somekey = ?',
[0, 1]
);
// offload from JS thread
await tx.executeAsync = tx.executeAsync(
'UPDATE sometable SET somecolumn = ? where somekey = ?',
[0, 1]
);
// Any uncatched error ROLLBACK transaction
throw new Error('Random Error!');
// You can manually commit or rollback
tx.commit();
// or
tx.rollback();
});Batch execution allows the transactional execution of a set of commands
const commands = [
['CREATE TABLE TEST (id integer)'],
['INSERT INTO TEST (id) VALUES (?)', [1]],
[('INSERT INTO TEST (id) VALUES (?)', [2])],
[('INSERT INTO TEST (id) VALUES (?)', [[3], [4], [5], [6]])],
];
const res = NitroSQLite.executeSqlBatch('myDatabase', commands);
console.log(`Batch affected ${result.rowsAffected} rows`);In some scenarios, dynamic applications may need to get some metadata information about the returned result set.
This can be done by testing the returned data directly, but in some cases may not be enough, for example when data is stored outside SQLite datatypes. When fetching data directly from tables or views linked to table columns, SQLite can identify the table declared types:
let { metadata } = NitroSQLite.executeSql(
'myDatabase',
'SELECT int_column_1, bol_column_2 FROM sometable'
);
metadata.forEach((column) => {
// Output:
// int_column_1 - INTEGER
// bol_column_2 - BOOLEAN
console.log(`${column.columnName} - ${column.columnDeclaredType}`);
});You might have too much SQL to process and it will cause your application to freeze. There are async versions for some of the operations. This will offload the SQLite processing to a different thread.
NitroSQLite.executeAsync(
'myDatabase',
'SELECT * FROM "User";',
[]).then(({rows}) => {
console.log('users', rows);
})
);SQLite supports attaching or detaching other database files into your main database connection through an alias. You can do any operation you like on this attached database like JOIN results across tables in different schemas, or update data or objects. These databases can have different configurations, like journal modes, and cache settings.
You can, at any moment, detach a database that you don't need anymore. You don't need to detach an attached database before closing your connection. Closing the main connection will detach any attached databases.
SQLite has a limit for attached databases: A default of 10, and a global max of 125
NitroSQLite.attach('mainDatabase', 'statistics', 'stats', '../databases');
const res = NitroSQLite.executeSql(
'mainDatabase',
'SELECT * FROM some_table_from_mainschema a INNER JOIN stats.some_table b on a.id_column = b.id_column'
);
// You can detach databases at any moment
NitroSQLite.detach('mainDatabase', 'stats');
if (!detachResult.status) {
// Database de-attached
}If you have a plain SQL file, you can load it directly, with low memory consumption.
const { rowsAffected, commands } = NitroSQLite.loadFile(
'myDatabase',
'/absolute/path/to/file.sql'
);Or use the async version which will load the file in another native thread
NitroSQLite.loadFileAsync('myDatabase', '/absolute/path/to/file.sql').then(
(res) => {
const { rowsAffected, commands } = res;
}
);On iOS you can use the embedded SQLite, when running pod-install add an environment flag:
Nitro_SQLITE_USE_PHONE_VERSION=1 npx pod-install
On Android, it is not possible to link (using C++) the embedded SQLite. It is also a bad idea due to vendor changes, old android bugs, etc. Unfortunately, this means this library will add some megabytes to your app size.
This library is pretty barebones, you can write all your SQL queries manually but for any large application, an ORM is recommended.
You can use this library as a driver for TypeORM. However, there are some incompatibilities you need to take care of first.
Starting on Node14 all files that need to be accessed by third-party modules need to be explicitly declared, TypeORM does not export its package.json which is needed by Metro, we need to expose it and make those changes "permanent" by using patch-package:
// package.json stuff up here
"exports": {
"./package.json": "./package.json", // ADD THIS
".": {
"types": "./index.d.ts",
// The rest of the package json hereAfter you have applied that change, do:
bun patch-package --exclude 'nothing' typeormNow every time you install your node_modules that line will be added.
Next, we need to trick TypeORM to resolve the dependency of react-native-sqlite-storage to react-native-nitro-sqlite, on your babel.config.js add the following:
plugins: [
// w/e plugin you already have
...,
[
'module-resolver',
{
alias: {
"react-native-sqlite-storage": "react-native-nitro-sqlite"
},
},
],
]You will need to install the babel module-resolver plugin:
bun add babel-plugin-module-resolverFinally, you will now be able to start the app without any metro/babel errors (you will also need to follow the instructions on how to setup TypeORM), now we can feed the driver into TypeORM:
import { typeORMDriver } from 'react-native-nitro-sqlite'
datasource = new DataSource({
type: 'react-native',
database: 'typeormdb',
location: '.',
driver: typeORMDriver,
entities: [...],
synchronize: true,
});The library creates/opens databases by appending the passed name plus, the documents directory on iOS and the files directory on Android, this differs from other SQL libraries (some place it in a www folder, some in androids databases folder, etc.).
If you have an existing database file you want to load you can navigate from these directories using dot notation. e.g. ../www/myDb.sqlite. Note that on iOS the file system is sand-boxed, so you cannot access files/directories outside your app bundle directories.
Alternatively, you can place/move your database file using one of the many react-native fs libraries.
By specifying pre-processor flags, you can enable optional features like FTS5, Geopoly, etc.
Add a post_install block to your <PROJECT_ROOT>/ios/Podfile like so:
post_install do |installer|
installer.pods_project.targets.each do |target|
if target.name == "react-native-nitro-sqlite" then
target.build_configurations.each do |config|
config.build_settings['GCC_PREPROCESSOR_DEFINITIONS'] << 'SQLITE_ENABLE_FTS5=1'
end
end
end
endReplace the <SQLITE_FLAGS> part with the flags you want to add.
For example, you could add SQLITE_ENABLE_FTS5=1 to GCC_PREPROCESSOR_DEFINITIONS to enable FTS5 in the iOS project.
You can specify flags via <PROJECT_ROOT>/android/gradle.properties like so:
nitroSqliteFlags="<SQLITE_FLAGS>"
On iOS, the SQLite database can be placed in an app group, in order to make it accessible from other apps in that app group. E.g. for sharing capabilities.
To use an app group, add the app group ID as the value for the RNNitroSQLite_AppGroup key in your project's Info.plist file. You'll also need to configure the app group in your project settings. (Xcode -> Project Settings -> Signing & Capabilities -> Add Capability -> App Groups)
Join the Margelo Community Discord to chat about react-native-nitro-sqlite or other Margelo libraries.
MIT License.
