Allow customizing Storage database name

[joekrill]

This allows overriding the filename used by the Key-Value Storage (from the default __opsqlite_storage.sqlite).

I'm not sure if there was any particular reason for not being able to override this?

[ospfranco]

what's the point of overriding this? The intention is to keep the API as simple as possible to avoid people messing up stuff

[joekrill]

what's the point of overriding this? The intention is to keep the API as simple as possible to avoid people messing up stuff

As an example: you may want a key-value store for app configuration items, and a separate one for cached data. The cached data can be deleted/wiped without affecting the app preferences.

It's already possible to create multiple instances - it's just that currently there's a requirement that they be in different locations. So this actually makes that use-case simpler and less complex in those cases.

[ospfranco]

eh... you might as well save your configurations under a different key than a whole new database?

This API was created as a convenience for people who didn't want to add another package like MMKV but it's meant to be simple and dumb AF... otherwise people mess up their dbs, get connection problems, memory problems and then they complain the package doesn't work