Hi. https://github.com/rust-lang/rust/pull/42125 is going to turn some old compatibility "private-in-public" warnings in rustc into hard errors. crates.io testing discovered that published version of this crate is affected by one of those errors. The problem seems to be fixed on the current master, could you push it on crates.io as couchdb-0.5.2? (Even if the crate is deprecated, it would still be useful for the compiler's regression testing.)

Our integration tests rely on starting and stopping a temporary CouchDB server. On Windows there are some problems doing this.

Consequently, the integration test get_view fails.

$ cargo test get_view
     Running target\debug\commands-8c77530f0accee12.exe

running 1 test
test get_view ... FAILED

failures:

---- get_view stdout ----
        thread 'get_view' panicked at 'called `Result::unwrap()` on an `Err` value: InternalServerError { response: ErrorResponse { error: "EXIT", reason: "{{badmatch,{error,{bad_return_value,{os_process_error,{exit_status,4}}}}},\n [{couch_query_servers,new_process,3,\n                       [{file,\"c:/cygwin/relax/APACHE~2.1/src/couchdb/couch_query_servers.erl\"},\n                        {line,477}]},\n  {couch_query_servers,lang_proc,3,\n                       [{file,\"c:/cygwin/relax/APACHE~2.1/src/couchdb/couch_query_servers.erl\"},\n{line,462}]},\n  {couch_query_servers,handle_call,3,\n[{file,\"c:/cygwin/relax/APACHE~2.1/src/couchdb/couch_query_servers.erl\"},\n                        {line,334}]},\n  {gen_server,handle_msg,5,[{file,\"gen_server.erl\"},{line,585}]},\n  {proc_lib,init_p_do_apply,3,[{file,\"proc_lib.erl\"},{line,239}]}]}" } }', ../src/libcore\result.rs:732

failures:
    get_view

test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured

thread '<main>' panicked at 'Some tests failed', ../src/libtest/lib.rs:252

Also, the integration tests assume CouchDB is installed in the default path. From src/server.rs:

c.arg("c:/program files (x86)/apache software foundation/couchdb/etc/couchdb/default.ini");
c.arg("c:/program files (x86)/apache software foundation/couchdb/etc/couchdb/local.ini");

Lastly, the tests run slowly, and CPU use for the test executable seems excessive.

Define DocumentId and DatabaseName types. These types would replace the &str type currently used for identifying documents and databases, thereby making our crate's API more type-safe.

Resuscitate this crate as a low-level interface to the CouchDB API and for Chill to be implemented using this crate.

The idea is for this crate to provide a one-to-one mapping between Rust and the CouchDB API (paths, query parameters, headers, etc.), while Chill would provide the same functionality but at a higher level, including such things as document/attachment management.

CouchDB uses different types in requests and responses for representing the same entity. For example, an embedded attachment contains different fields as a request originating from the client (e.g., the follows field) than as a response originating from the server (e.g.., the digest field). Currently, our crate's API uses strong types for responses and a quasi builder pattern when constructing requests.

It may be better to use strong types for both requests and responses.

This issue tracks the design and implementation of strong types for request- and response-specific types.

Here is a list of types for consideration:

• Documents, retrieved via GET /db/doc and updated via PUT /db/doc.
• Embedded attachments, retrieved via GET /db/doc and updated via PUT /db/doc.
• Standalone attachments, retrieved via GET /db/doc/attachment and updated via PUT /db/doc/attachment.

Currently, the GetChanges action has two methods for setting the heartbeat query parameter: heartbeat and default_heartbeat. This is a workaround for using a std::time::Duration type to represent the heartbeat value because the duration type cannot express the valid parameter value of true. The true value explicitly signifies a default heartbeat value.

Wrap the std::time::Duration type in a special type for representing all heartbeat values, and consolidate the two heartbeat methods into one method.

Add an action to POST a view (e.g., /db/_design/design-doc/_view/view-name). The POST action is the same as the GET action but with a request body that specifies which keys the server should include in the response.

CouchDB revisions comprise a number followed by a hash value. A revision with a smaller number is less than a revision with a bigger number.

However, the Revision type compares the number parts lexicographically. E.g., 7 should be less than 13, but the Revision type orders 13 before 7 because the character '1' is less than the character '7'.

The following program demonstrates the problem by failing the assertion:

let r1 = couchdb::Revision::from("7-12345678123456781234567812345678");
let r2 = couchdb::Revision::from("13-12345678123456781234567812345678");
assert!(r1 < r2);

Add support for CouchDB filter functions.

The use of filter functions depends upon the implementation of change notifications (issue #12).

This issue excludes adding support for built-in filters (i.e., _doc_ids, _design, and _view).

Add support for running commands asynchronously, meaning the method to run the command returns immediately and the command result is returned to the application via some other means, such as by callback.

The couchdb crate currently requires applications to use serde to serialize and deserialize JSON—e.g., document content, view keys, etc.

At a minimum, the couchdb crate should also support rustc_serialize. Possibly the couchdb crate should support all serialization and deserialization techniques an application may use.

Hello, where I can find some example how to use this lib.

I simply need to connect to db and register handler for changes.

Documentation does not explain it directly.

Currently, the Travis CI builds don't run documentation tests. This is because Cargo runs documentation tests only if the command line specifies no test filter. However, we use the test filter --lib to avoid running any integration tests, which would fail because the Travis CI build agent doesn't have a CouchDB server installed.

Therefore, resolving this issue will require better support for running documentation tests using Cargo.