Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of pauloedgarcastro@gmail.com
 designates 209.85.212.173 as permitted sender)
Message-ID: <50DE1F4D.6060500@gmail.com>
Date: Fri, 28 Dec 2012 22:38:05 +0000
From: Paulo Edgar Castro <pauloedgarcastro@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:15.0) Gecko/20120911 Thunderbird/15.0.1
MIME-Version: 1.0
To: user@couchdb.apache.org
Subject: Bad special document member: __VERSION__
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi all,

I just bumped into this error in the subject.
Upon further digging as per commit 
d748a328aec166047c81bcaf3dec6b0a885a2088, keys starting with an 
underscore are not accepted as valid...

DB="http://127.0.0.1:5984/mydb"
curl -X PUT $DB
curl -H "Content-Type:application/json"  -d 
'{"docs":[{"key":"baz","_name":"bazzel"},{"key":"bar","_name":"barry"}]}' -X 
POST $DB/_bulk_docs

{"error":"doc_validation","reason":"Bad special document member: _name"}

Some modules I'm using as part of a project try to serialize a whole 
class and some of the keys are serialized with underscores.
This means that CouchDB stops being an option for storage.

Is there a good reason for this design decision ?
Couldn't the underscore keys be validated against the set of reserved 
words or similar ?
Could this be something not serving a useful purpose ?

Also, I couldn't find any meaningful caveat about this in the wiki ...

Regards,


                 PECastro