db.destroy doesn't work on memdown created with {db: require('memdown')}

[calvinmetcalf]

No description provided.

[jacargentina]

Just confirming... it is possible that the bug is aplicable to any PouchDB instance using a custom {db: require('...') } options, which are not used on the 'new' pouchdb instance created when destroy is called ?

[calvinmetcalf]

right it's if you pass it in as an option

[jacargentina]

@calvinmetcalf I'have another bug, when using this commit. Maybe u can fix it faster than i can, and kill 2 birds from a single shot :-)

This simply code fails on Node, when using db: { require('sqldown') }

var PouchDB = require('pouchdb');

var pouch = new PouchDB('test.db', {
  db: require('sqldown')
});

pouch.put({
  _id: '_design/test',
  views: {
    test: {
      map: function(doc) {
        return doc;
      }.toString()
    }
  }
}).then(function() {
  pouch.destroy()
    .then(function() {
      console.log('ok ');
    })
    .catch(function(err) {
      console.log('error ', err);
    });
});

I'get the error:

error  { [Error: EBUSY, unlink 'C:\Git\project\test.db']
  errno: 10,
  code: 'EBUSY',
  path: 'C:\\Git\\project\\test.db' }

Maybe the destroy code for other adapters are missing some "close all files" before actually destroying?

[calvinmetcalf]

um I think that is an error in sqldown

[calvinmetcalf]

beb3a6e