Return-Path: X-Original-To: apmail-couchdb-dev-archive@www.apache.org Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 61027F13D for ; Wed, 27 Mar 2013 16:57:17 +0000 (UTC) Received: (qmail 49176 invoked by uid 500); 27 Mar 2013 16:57:16 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 49121 invoked by uid 500); 27 Mar 2013 16:57:16 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 48941 invoked by uid 99); 27 Mar 2013 16:57:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Mar 2013 16:57:15 +0000 Date: Wed, 27 Mar 2013 16:57:15 +0000 (UTC) From: "Dave Cottlehuber (JIRA)" To: dev@couchdb.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (COUCHDB-1725) Remove reserved metadata from documents MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/COUCHDB-1725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Cottlehuber updated COUCHDB-1725: -------------------------------------- Labels: couchdb erlang gsoc2013 rest (was: couchdb, erlang, gsoc2013, rest,) > Remove reserved metadata from documents > --------------------------------------- > > Key: COUCHDB-1725 > URL: https://issues.apache.org/jira/browse/COUCHDB-1725 > Project: CouchDB > Issue Type: Improvement > Reporter: Dave Cottlehuber > Labels: couchdb, erlang, gsoc2013, rest > > CouchDB treats some fields specially (_id, _rev, _attachments), > requiring a transformation process when reading and writing documents. > Removing the fields would allow higher performance and alternative > data types. A question remains as to where they would go, as not all > map to a standard HTTP header (_rev maps neatly to ETag, > though). Custom HTTP headers is an obvious solution, are there others? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira