Additional Example

[jimthedev]

Hi there,

One super useful example might be, how to use a single database, but multiple stores.

The current example shows that database and store are set in the same config. If you had multiple stores inside of one database, it would be worthwhile to see how you could set the database at the app level, and set individual stores at the service level.

Is this something that'd be possible?

[ocombe]

I'm not entirely sure of what you mean ?
Localforage might use localstorage if indexedDB or webSQL ain't available, and localstorage only handles key-values.
My module will add a prefix to be sure that your data can be manipulated independently from other data (ie: you won't wipe other libs localstorage data).
If you need to store different things, use different keys.

If you are referring to the way indexedDB stores its data with a database, multiple tables with multiple keys in each, it is not possible because we need to make sure that it would work just the same for localstorage. Localforage will only use one database and one table (but multiple keys, of course).

[jimthedev]

@ocombe Ok gotcha. I will just use keys instead. I thought maybe there was the potential to use one db but multiple tables but was wrong. Thanks for the help and this awesome project. One unrelated question, have you used a cache with this at all? Something similar to angular-cache or other cache projects?

[ocombe]

I haven't used any cache no, I think it should be something devs need to implement on their own because I don't know what their needs are :)
And thanks for the credit but most of the hard work has been done by @tofumatt in https://github.com/mozilla/localForage, this is (almost) just an angular wrapper :)