Maybe I missed how to do this, but I would like to be able to specify the directory used to store the sqlite files created when using the idb adapter. Seems like current functionality only allows the cwd?

On a hunch, I took a shot at just using prefix like what is described in Pouch docs with respect to LevelDB, but the result is the sqlite file name is prefixed:

// results in a file in cwd named D__pouch_^12fpath^12fto^12ffilefoobar.sqlite
new PouchDB.defaults({ adapter: 'idb', prefix: '/path/to/file'})("foobar")

My use case is that I would like to be able to place the files into a directory, that the Deno task has permissions to write to ie. deno run --allow-write=/tmp/foo --allow-read=/tmp/foo foo.js

Thanks!

I was getting a stack of errors (below) related to a missing callback, when running your couch port in the browser. Although I don't think browser usage was your intent I wanted to see if I could get it working.

That said, I'm also importing this modified version of your port for a node-side instance of couch and it seems to be ok.

From what I could see, declaring this as an arg in the function being run via call was causing the arguments to shift, so that the value of this was the options and the value of opts was the callback (for me anyways).

This change seems to have unblocked things and I can now see the db created in the "browser storage inspector" (firefox).

The error(s): Uncaught TypeError: fun is not a function tryCode pouchdb-adapter-idb.js:786 runCallback pouchdb-adapter-idb.js:801 completeSetup pouchdb-adapter-idb.js:1511 oncomplete pouchdb-adapter-idb.js:1543 onsuccess pouchdb-adapter-idb.js:1541 init pouchdb-adapter-idb.js:1476 IdbPouch pouchdb-adapter-idb.js:969 runAction pouchdb-adapter-idb.js:800 applyNext pouchdb-adapter-idb.js:796 enqueueTask pouchdb-adapter-idb.js:808 IdbPouch pouchdb-adapter-idb.js:968 idb mod.ts:41 PouchDB pouchdb-core.js:1401

Since this project tries to simply re-export PouchDB, it would be good to co-version releases with the parent code. However, I foresee the need to implement bugfixed in the work-arounds and polyfills. A few ideas:

• Break out WebSQL and IndexedDB polyfills into their own repo for independent versioning
• Add a semver tag with own version, e.g. 7.2.2-DENOv1.0.0
• Invert the tag relationship, like 1.0.0-POUCHDBv7.2.2
• Version completely independent of PouchDB, and notify users of Pouch version changes via README

Would happily take feedback and any other ideas out there.

Firstly, really awesome work here. I'm so excited to be able to use PouchDB in Deno!

Something I came across, maybe I am missing something, it seems that operations hang when using the idb adapter. That is to say, the Promise never resolves.

Reproduce:

import PouchDB from "https://deno.land/x/[email protected]+7.2.2/modules/pouchdb/mod.ts";

const db = new PouchDB('foobar', { adapter: 'idb' })

console.log(db)

// This Promise seems to never resolve
console.log(await db.post({
  name: 'foo'
}))

console.log(await db.find({ selector: { name: 'foo' }}))

I am able to use the memory adapter and things seem to work, so seems like something with idb polyfill?

Thanks again.

• [x] Include new feature to set directory path(s) for user and system IndexedDB sqlite databases #7
• [x] Upgrade all dependencies to latest, but specifically PouchDB 7.3.0
• [x] Expose the new BETA-quality indexeddb adapter; the Pouch team expect it to eventually replace idb
• [x] Release to Denoland as 2.0.0-PouchDB+7.3.0

• [x] Move WebSQL to https://github.com/aaronhuggins/websql
• [x] Move IndexedDB to https://github.com/aaronhuggins/indexeddb
• [x] Publish modules to https://deno.land/x
• [x] Update imports for IndexedDB and WebSQL in repository to new URLs

• [x] Explain usage of the main export
• [x] Describe caveats for Deno
• [x] Add links back to original PouchDB repository and packages, give proper credit
• [x] Flesh out IndexedDB Shim pony/polyfill README
• [x] Flesh out WebSQL ponyfill README
• [x] Add license file (MIT)

Currently, on a hot-load, importing the main PouchDB module in this repository takes between 4.4 and 9.9 seconds. This module load time needs to be reduced.

• [x] Experiment with plugin capture of idb adapter (would reduce network traversals and import evaluations by 18)
• [x] Experiment with plugin capture of find plugin
• [x] Research other bundled plugins