I did not see that thread when I opened the constant naming unification.
I am a bit skeptical that option should be used for global settings like host
and co but let's try and see where that leads us.
On 11 déc. 2013, at 18:36, "Davide D'Alto" wrote:
>> Our question is, should now that we ha
> Our question is, should now that we have the Option API and with it
store-specific DatastoreConfiguration types, the previously used
Environment interfaces be removed and their constants moved to the
corresponding DatastoreConfiguration type?
Yes, +1
On Wed, Dec 11, 2013 at 5:08 PM, Gunnar Mo
Hi,
Davide brought up an interesting issue while reviewing a PR around the OGM
backend for CouchDB [1].
This PR makes use of the new Option API and allows to configure
CouchDB-specific settings in a safe way. For that purpose each dialect
needs to provide a sub-class of DatastoreConfiguration whi
