ueberdb2 4.1.44 → 4.2.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +23 -21
- package/dist/index.js +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -26,7 +26,8 @@ writes are done in a bulk. This can be turned off.
|
|
|
26
26
|
* Redis
|
|
27
27
|
* Rethink
|
|
28
28
|
* SQLite
|
|
29
|
-
|
|
29
|
+
* Surrealdb
|
|
30
|
+
*
|
|
30
31
|
## Install
|
|
31
32
|
|
|
32
33
|
```
|
|
@@ -208,19 +209,20 @@ const ueberdb = require('ueberdb2');
|
|
|
208
209
|
|
|
209
210
|
## Feature support
|
|
210
211
|
|
|
211
|
-
|
|
|
212
|
-
|
|
213
|
-
|
|
|
214
|
-
|
|
|
215
|
-
|
|
|
216
|
-
|
|
|
217
|
-
|
|
|
218
|
-
|
|
|
219
|
-
|
|
|
220
|
-
|
|
|
221
|
-
|
|
|
222
|
-
|
|
|
223
|
-
|
|
|
212
|
+
| | Get | Set | findKeys | Remove | getSub | setSub | doBulk | CI Coverage |
|
|
213
|
+
|---------------|-----|-----|----------|--------|--------|--------|--------|-------------|
|
|
214
|
+
| cassandra | ✓ | ✓ | * | ✓ | ✓ | ✓ | ✓ | |
|
|
215
|
+
| couchdb | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | |
|
|
216
|
+
| dirty | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | | ✓ |
|
|
217
|
+
| dirty_git | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | | |
|
|
218
|
+
| elasticsearch | ✓ | ✓ | * | ✓ | ✓ | ✓ | ✓ | |
|
|
219
|
+
| maria | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | |
|
|
220
|
+
| mysql | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
|
|
221
|
+
| postgres | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
|
|
222
|
+
| redis | ✓ | ✓ | * | ✓ | ✓ | ✓ | ✓ | ✓ |
|
|
223
|
+
| rethinkdb | ✓ | ✓ | * | ✓ | ✓ | ✓ | ✓ |
|
|
224
|
+
| sqlite | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
|
|
225
|
+
| surrealdb | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | |
|
|
224
226
|
|
|
225
227
|
## Limitations
|
|
226
228
|
|
|
@@ -286,16 +288,16 @@ environment variable `NODE_TLS_REJECT_UNAUTHORIZED = 0` and add the flag
|
|
|
286
288
|
|
|
287
289
|
1. Add the database driver to `packages.json`, this will happen automatically if
|
|
288
290
|
you run `npm install %yourdatabase%`
|
|
289
|
-
|
|
291
|
+
2. Create `databases/DATABASENAME_db.js` and have it export a `Database` class
|
|
290
292
|
that derives from `lib/AbstractDatabase.js`. Implement the required
|
|
291
293
|
functions.
|
|
292
|
-
|
|
294
|
+
3. Add a service for the database to the test job in
|
|
293
295
|
`.github/workflows/npmpublish.yml`.
|
|
294
|
-
|
|
296
|
+
4. Add an entry to `test/lib/databases.js` for your database and configure it to
|
|
295
297
|
work with the service added to the GitHub workflow.
|
|
296
|
-
|
|
298
|
+
5. Install and start the database server and configure it to work with the
|
|
297
299
|
settings in your `test/lib/databases.js` entry.
|
|
298
|
-
|
|
300
|
+
6. Run `npm test` to ensure that it works.
|
|
299
301
|
|
|
300
302
|
## License
|
|
301
303
|
|
|
@@ -323,5 +325,5 @@ Dirty_git will `commit` and `push` to Git on every `set`. To use `git init` or
|
|
|
323
325
|
`git clone` within your dirty database location and then set your upstream IE
|
|
324
326
|
`git remote add origin git://whztevz`.
|
|
325
327
|
|
|
326
|
-
The logic behind dirty git is that you can still use dirty but you can also have
|
|
327
|
-
offsite backups. It's noisy and spammy but it can be useful.
|
|
328
|
+
The logic behind dirty git is that you can still use dirty, but you can also have
|
|
329
|
+
offsite backups. It's noisy and spammy, but it can be useful.
|