Enable store file name different from model file name

[gfpacheco]

I'm building an app that needs multiples stores with the same data model. This optional init parameter enables such case.

[3lvis]

Hi @gfpacheco,

This looks good, I'll look into adding a few unit tests to ensure it doesn't break in the future.

[3lvis]

Hey! Do you have an example on how are you using this? I'm having a hard time to come up with a use case.

[gfpacheco]

Well, in my case I build apps for events. Usually there's one app for each event. There's this customer that wants one app for some of his events. Then I built another db scheme for the shared part of the app and each event keeps using the exact same scheme. When the user selects one event, I open the event's store and bring the details for that one.

[3lvis]

What's different between the modelName and the storeName, then? Seems like they are the same.

[3lvis]

Oh, wait, I got it now. Thanks 😊

[gfpacheco]

Hahah, just to clarify for anyone who get here: model name is the database scheme file name, store name is the name of the sqlite store file. I can have multiples stores using the same db scheme =]

[3lvis]

Released on 4.1.0

🌟 🌟 Thanks 👏 🌟 🌟