> On 5. Jul 2018, at 13:54, Mad, Pink and Dangerous to Know <p...@mad.pink>
> wrote:
>
> This isn't really a "fix" per se, but one of the reasons I still use
> CouchDB 1.x is the change log. I have a homemade local syncing library for
> Livecode that I use that is heavily dependent on the old _changes api. I've
> been working on changing it for 2.x, but it involves having to add my own
> version of the change log to documents as they are being written)
>
> I understand why it was changed, but it would be great if there were a
> similar system available in 2.x
This is a great point!
It is regrettable, that 1.x had undefined behaviour that we had to give up
for 2.x, that folks relied on early on. It is the main one of the very few API
design mistakes we’ve made (IMHO), but there is no way to add 1.x behaviour to
2.x (although q=1 and n=1 will get you close).
Best
Jan
—
>
> On Thu, Jul 5, 2018 at 3:10 AM Johs Ensby <j...@b2w.com> wrote:
>
>> This thread reach out to CouchDB 1.x users to generate a list of
>> "must-fix" issues that is preventing users to upgrade to the latest
>> version of CouchDB.
>>
>> It is in response to Joan's comment below regarding the
>> non-technical proposal to make a project decision to terminate
>> official Apache support for CouchDB 1.x.
>>
>>> On 5 Jul 2018, at 06:31, Joan Touzet <woh...@apache.org> wrote:
>>>
>>> As for things in 2.x that are "must fix" before people can upgrade, I
>>> too would like to see pull requests for those. Once again, your help is
>>> most welcome in this - both in identifying a definitive list of those
>>> must-fix issues, as well as code towards fixing them. If you'd like
>>> to help with this important work, please start a new thread.
>>
>>
>>
>> Mine is CouchDB as a proxy.
>> The feature described here is not working in 2.1.1
>> http://docs.couchdb.org/en/2.1.1/config/proxying.html?highlight=_proxy
>>
>> Johs
>>
--
Professional Support for Apache CouchDB:
https://neighbourhood.ie/couchdb-support/
