OAuth secrets can now be stored in the users system database
as an alternative to key value pairs in the .ini configuration.
By default this is disabled (secrets are stored in the .ini)
but can be enabled via the .ini configuration key use_users_db
in the couch_httpd_oauth section.
Documents in the _users database are no longer publicly
Confidential information in the _replication database is no
longer publicly readable.
Password hashes are now calculated by CouchDB. Clients are no
longer required to do this manually.
Cookies used for authentication can be made persistent by enabling
the .ini configuration key allow_persistent_cookies in the
cURL is no longer required to build CouchDB as it is only
used by the command line JS test runner. If cURL is available
when building CouchJS you can enable the HTTP bindings by
passing -H on the command line.
Temporarily made make check pass with R15B. A more thorough
fix is in the works (COUCHDB-1424).
Added optional database and view index file compression (using Google’s
snappy or zlib’s deflate). This feature is enabled by default, but it
can be disabled by adapting local.ini accordingly. The on-disk format
is upgraded on compaction and new DB/view creation to support this.
Several performance improvements, most notably regarding database writes
and view indexing.
Computation of the size of the latest MVCC snapshot data and all its
supporting metadata, both for database and view index files. This
information is exposed as the data_size attribute in the database and
view group information URIs.
The size of the buffers used for database and view compaction is now
Added support for automatic database and view compaction. This feature
is disabled by default, but it can be enabled via the .ini configuration.
Performance improvements for the built-in changes feed filters _doc_ids
JSON strings are now displayed as-is in the document view, without the
escaping of new-lines and quotes. That dramatically improves readability of
Same goes for editing of JSON string values. When a change to a field value is
submitted, and the value is not valid JSON it is assumed to be a string. This
improves editing of multi-line strings a lot.
Hitting tab in textareas no longer moves focus to the next form field, but
simply inserts a tab character at the current caret position.
Added optional ‘raw’ binary collation for faster view builds where Unicode
collation is not important.
Improved view index build time by reducing ICU collation callouts.
Improved view information objects.
Bug fix for partial updates during view builds.
Move query server to a design-doc based protocol.
Use json2.js for JSON serialization for compatiblity with native JSON.
Major refactoring of couchjs to lay the groundwork for disabling cURL
support. The new HTTP interaction acts like a synchronous XHR. Example usage
Fix for replication problems where the write queues can get backed up if the
writes aren’t happening fast enough to keep up with the reads. For a large
replication, this can exhaust memory and crash, or slow down the machine
dramatically. The fix keeps only one document in the write queue at a time.
Fix for databases sometimes incorrectly reporting that they contain 0
documents after compaction.
CouchDB now uses ibrowse instead of inets for its internal HTTP client
implementation. This means better replication stability.
When adding a field to a document, Futon now just adds a field with an
autogenerated name instead of prompting for the name with a dialog. The name
is automatically put into edit mode so that it can be changed immediately.
Fields are now sorted alphabetically by name when a document is displayed.
Futon can be used to create and update permanent views.
The maximum number of rows to display per page on the database page can now
Futon now uses the XMLHTTPRequest API asynchronously to communicate with the
CouchDB HTTP server, so that most operations no longer block the browser.
View results sorting can now be switched between ascending and descending by
clicking on the Key column header.
Fixed a bug where documents that contained a @ character could not be
The database page now provides a Compact button to trigger database
Fixed portential double encoding of document IDs and other URI segments in
many instances. (COUCHDB-39)
Improved display of attachments.
SpiderMonkey is no longer included with CouchDB, but rather treated as a
normal external dependency. A simple C program (_couchjs) is provided that
links against an existing SpiderMonkey installation and uses the interpreter
using the global log(message) function. Log messages are directed into the
CouchDB log at INFO level. (COUCHDB-59)
The global map(key, value) function made available to view code has been
renamed to emit(key, value).
Fixed handling of exceptions raised by view functions.
CouchDB now uses MochiWeb instead of inets for the HTTP server
implementation. Among other things, this means that the extra configuration
files needed for inets (such as couch_httpd.conf) are no longer used.
The HTTP interface now completely supports the HEAD method. (COUCHDB-3)
Improved compliance of Etag handling with the HTTP specification.
Etags are no longer included in responses to document GET requests that
include query string parameters causing the JSON response to change without
the revision or the URI having changed.
The bulk document update API has changed slightly on both the request and the
response side. In addition, bulk updates are now atomic.
CouchDB now uses TCP_NODELAY to fix performance problems with persistent
connections on some platforms due to nagling.
Including a ?descending=false query string parameter in requests to views
no longer raises an error.
Requests to unknown top-level reserved URLs (anything with a leading
underscore) now return a unknown_private_path error instead of the
The Temporary view handling now expects a JSON request body, where the JSON
is an object with at least a map member, and optional reduce and
Temporary views no longer determine the view server based on the Content-Type
header of the POST request, but rather by looking for a language member
in the JSON body of the request.
The status code of responses to DELETE requests is now 200 to reflect that
that the deletion is performed synchronously.