On Fri, Jan 16, 2009 at 10:54 PM, Patrick Antivackis
patrick.antivac...@gmail.com wrote:
Damien,
For what i saw in previous tests, if you not use the chunk method, then you
get an error caught by mochiweb (so no error in couchdb).
It occurs in mochiweb_request line 138 with the gen_tcp:recv
Hello!
I'm writing some multi-app hosting thing and besides using couchdb as
database it also stores all images and stylesheets and scripts etc for
the applications as attachments. I have one couchdb database per app and
store all resources on a single document to keep the same relative
[
https://issues.apache.org/jira/browse/COUCHDB-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bob Dionne updated COUCHDB-212:
---
Attachment: couch_js.c.diff
PUT requests now require file size be sent to couchdb for the new
On Fri, Jan 16, 2009 at 11:54:04PM +0100, Jan Lehnardt wrote:
The three committers Chris Anderson, Noah Slater and Jan Lehnardt
started releasing chapters from their work-in-progress book CouchDB:
The Definitive Guide on http://books.couchdb.org/ The content will be
licensed under Apache 2.0
On 17 Jan 2009, at 18:18, Noah Slater wrote:
On Fri, Jan 16, 2009 at 11:54:04PM +0100, Jan Lehnardt wrote:
The three committers Chris Anderson, Noah Slater and Jan Lehnardt
started releasing chapters from their work-in-progress book CouchDB:
The Definitive Guide on http://books.couchdb.org/
config test failure for ports 80 and 443
Key: COUCHDB-213
URL: https://issues.apache.org/jira/browse/COUCHDB-213
Project: CouchDB
Issue Type: Bug
Components: Test Suite
Hi dev list, Damien,
I noticed when a database has multiple design docs with a
`validate_doc_update` function each. The validation functions
are called in the reverse string collation order of the design
document's id.
The function in `_design/b` gets executed before the one
in `_design/a`,
Jan,
My gut feeling is that this ordering should be specified as undefined.
The assumption being that users need to make sure their design docs
don't rely on any given ordering.
Either that, or provide a mechanism for people to order their docs
arbitrarily. I'd lean towards the first because its
On Sat, Jan 17, 2009 at 1:49 PM, Paul Davis paul.joseph.da...@gmail.com wrote:
Jan,
My gut feeling is that this ordering should be specified as undefined.
The assumption being that users need to make sure their design docs
don't rely on any given ordering.
Agreed. Each validation should
