Problem in Safari Mobile with destroy DB

[D4v1X]

Scene:

-iPad air 2 & iPhone 6 Plus
-AngularJS: 1.4.8.
-Safari Mobile: last version
-pouchdb: 5.1.0

User case:

I inserted some objects in the database, and then I executed the destroy function and I am creating the empty database again, but when I search documents in the database I can recover the old data.

Why not is empty?
there is a problem?
Am I doing something wrong?

NOTE: without fruitdown and chrome in PC works fine.

1.Step:

var DB_NAME = 'Client';
var databaseConnection = new PouchDB(DB_NAME, {adapter: 'fruitdown'});
//insert 9 Objects
return databaseConnection.allDocs ({include_docs: true}).then (function (docsFromDatabase) {});
//return 9 Objets

2.Step:

function purge() {
    return new PouchDB(DB_NAME).destroy().then(function () {
        databaseConnection = new PouchDB(DB_NAME, {adapter: 'fruitdown'});
        return databaseConnection;
    });
}

3.Step:

return databaseConnection.allDocs ({include_docs: true}).then (function (docsFromDatabase) {});
//return 9 Objects why?

[nolanlawson]

You might have discovered a bug in Safari. It's hard to say, though - this plugin passes the full PouchDB test suite on iOS 8.4, which pretty aggressively uses db.destroy(). (It does it before and after every test, and there are ~1500 tests.)

If you could provide a reproducible test case to run, then that would be helpful. :)

[ronycohen]

Hello,

I encounter a similar issue but not with FruitDown, with WebSQL

1. The destroy on Safari is working => No Db available in the Safari Inspector.

2. There I launch a window.location.reload(true) in order to clean everything.

3. When Recreating the Same DB with same Name => The datas from the previous destroyed DB are available.

This use Case does probably not exist in your test set.

[nolanlawson]

@ronyrun Can you reproduce this with pure WebSQL commands? If so, please file an issue on the WebKit bug tracker.

[ronycohen]

done

[nolanlawson]

@ronyrun Can you post a link to the issue you filed on WebKit? Curious to know more.

[ronycohen]

https://bugs.webkit.org/show_bug.cgi?id=156501

[nolanlawson]

It says "You are not authorized to access bug #156501," but that's okay, no worries.

[nolanlawson]

This issue still needs a reproducible test case.