how to use non-default localforage instance?

[siddo420]

how do I use separate localforage instances (instead of localforage)?

I am thinking of creating different instances per user (makes sense on installed apps).

Ref: https://github.com/mozilla/localForage#multiple-instances

[tofumatt]

I don't think localForage-backbone supports multiple instances yet. If you just want to change the db name per user you should be able to do that with the configuration.

Multiple instances are more useful when needing to deal with different sets of data at the same time. If you don't have multiple users signed in at once it might be overkill.

• tofumatt (Sent from mobile)

On 9 Nov 2015, at 16:35, siddo420 [email protected] wrote:

how do I use separate localforage instances (instead of localforage)?

I am thinking of creating different instances per user (makes sense on installed apps).

Ref: https://github.com/mozilla/localForage#multiple-instances

—
Reply to this email directly or view it on GitHub.

[siddo420]

Makes sense, I will try that.

However, is it possible to switch stores through localforage.config or I need to close the existing/open store first? I don't know how to close and reopen a store once driver has been set.

[tofumatt]

Once it has been set you can’t change the store, so if you want to change the store or database name with a page refresh, you WILL want to try multiple instances. That will require a patch to localforage-backbone, I think.

[siddo420]

I tried something that seems to work without breaking existing code.

Here are the relevant, small changes I made (on top of many others).

    Backbone.LFFactory = function( instance ){
     return {
        localforageInstance: instance,
...

Then, I changed all locarforage instances to this.localforageInstance (inside save, update, find etc methods ).

Before returning (at the bottom):

...
    Backbone.localforage = Backbone.LFFactory( localforage );
    return Backbone.localforage;
..

So Backbone.localforage still uses the default localforage variable and for separate instances, I do:

var lf_instance = localforage.createInstance(...);
..
sync: Backbone.LFFactory( lf_instance ).sync('Accounts') // accounts collection

Can you think of any issues?

[stephanebachelier]

@siddo420 I've not played with multiple instance of localforage instance but I've already managed to play with different stores. I mean I was able to switch between localstorage, websql and indexeddb depending on what the device supports. This was only made for a testing.