Unify open and openInMemory with Location type

[blaix]

Closes #46

Thoughts on adding a ConnectionString variant? It could just be a pass-thru to DatabaseSync. That would make it a lot easier to configure the registry with environment variables for deployment. I'm torn because that's a pretty raw approach, and a true Uri option would be better, but it doesn't look like node's sqlite supports sqlite's uri config.

[robinheghan]

Thoughts on adding a ConnectionString variant?

It's an option, but I'm also hesitant. One of the things that makes me hesitant is that you can pass query params to set certain options, which can override or be overriden by the options record you pass to Sqlite.open. Not sure if that's a good idea :/

[blaix]

One of the things that makes me hesitant is that you can pass query params to set certain options

That's supported via Sqlite URIs but I don't think it is supported by the node API, which says the string has to be a file path or ":memory:". Which is why I was thinking ConnectionString instead of URI. But still probably too ambiguous.

Maybe a function like parseUri would be better. It could return an Options record. And location could be moved from its own parameter to a field on the options record.

[blaix]

I don't think I like moving location into the options. And a connection string that is node-api-specific doesn't feel right either. Happy to merge this as-is soon unless you have thoughts.

[robinheghan]

I'm happy to merge this.