You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 8, 2025. It is now read-only.
Repository navigation
This repository was archived by the owner on Sep 8, 2025. It is now read-only.
It looks like several changes are needed. There's the new query system which uses a declarative syntax instead of map reduce, there are no more temporary views, and some API endpoints appear to have changed.
I closed the issue after realizing it may be outside the scope of this project (maybe a couchdb2-python fork is in order?).
Some developers don't like to support multiple major versions within one project simultaneously. It's your choice. I didn't feel it was my place to say this project should support Couch 1 AND Couch 2.
Did this conversation progress at all? I'm starting a new CouchDB 2.0 project. I've been using this project as a pip install to get me started and it's been working fairly well. However I'm starting to hit a few areas now where I want to take advantage of 2.0 features such as the Mango query language and proper support for the Erlang query server. (Please do correct me if I am wrong - I am new to CouchDB). Is there a recommended Github project for working with 2.0 or are there plans to support it here?
@danballance I have no plans to support it proactively in this project, but I'm open to merging patches for 2.0 support, as long as they don't remove 1.x support. I don't know of any other good projects you might use.
So most things are working fine with 2.0. Locally I now have a working branch for #300. It still needs tests and docstrings, so I'll do some more testing and try to get a pull request together before too long. I don't see it clashing with the existing code at all.
If I have some free time I may try and take a look at #308 but since it's not an issue that has hit me I'm not sure when I'll have time either. Let's see how my PR goes and take it from there I guess.
Activity
djc commentedon Sep 30, 2016
Does this mean no changes were needed to support CouchDB 2?
adrian-the-git commentedon Oct 1, 2016
It looks like several changes are needed. There's the new query system which uses a declarative syntax instead of map reduce, there are no more temporary views, and some API endpoints appear to have changed.
I closed the issue after realizing it may be outside the scope of this project (maybe a couchdb2-python fork is in order?).
djc commentedon Oct 1, 2016
I don't think it's outside of this project, why do you think so?
adrian-the-git commentedon Oct 8, 2016
Some developers don't like to support multiple major versions within one project simultaneously. It's your choice. I didn't feel it was my place to say this project should support Couch 1 AND Couch 2.
djc commentedon Oct 9, 2016
In principle I haven't seen anything so far that would make it hard to support CouchDB 2 from the same code base.
danballance commentedon Nov 2, 2016
Hi guys,
Did this conversation progress at all? I'm starting a new CouchDB 2.0 project. I've been using this project as a pip install to get me started and it's been working fairly well. However I'm starting to hit a few areas now where I want to take advantage of 2.0 features such as the Mango query language and proper support for the Erlang query server. (Please do correct me if I am wrong - I am new to CouchDB). Is there a recommended Github project for working with 2.0 or are there plans to support it here?
djc commentedon Nov 2, 2016
@danballance I have no plans to support it proactively in this project, but I'm open to merging patches for 2.0 support, as long as they don't remove 1.x support. I don't know of any other good projects you might use.
rdbisme commentedon Nov 2, 2016
@danballance See also #308. Still did not have the time to investigate on that.
danballance commentedon Nov 2, 2016
So most things are working fine with 2.0. Locally I now have a working branch for #300. It still needs tests and docstrings, so I'll do some more testing and try to get a pull request together before too long. I don't see it clashing with the existing code at all.
If I have some free time I may try and take a look at #308 but since it's not an issue that has hit me I'm not sure when I'll have time either. Let's see how my PR goes and take it from there I guess.
chaitanya9186 commentedon Nov 2, 2016
There is a python project which almost support Couchdb 2.0, https://github.com/cloudant/python-cloudant. It has other features as well though.