Github user kxepal commented on the pull request:
https://github.com/apache/couchdb-fabric/pull/33#issuecomment-179768803
@lazedo I think there is no practically need: these options could be
fetched within att_store/2 transparently for the API user during driver resolve
and without abstraction leaks.
Assume we have per-db driver configuration. Where such options will be
stored? First case: in config. Then we do `Driver = get_backend_driver(Db)` and
`Options = get_backend_driver_options(Db, Driver)` right before do any driver
API call. Another case: db options are stored in _metadata db - but this
changes nothing, only configuration backend. What else Options could be passed
here?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
