Mailing-List: contact couchdb-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: couchdb-user@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of gilbertbgarza@gmail.com
 designates 64.233.182.188 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version
         :content-type:references;
        b=q2ZJUAWc/sSP7XEgq1nztPZs9eUVvBZWTtl3icQzRLf1iBJAPkTu/zHomY146sZW5d
         pfkIMMbH8pZ19PMINzIRtEa2mDuW6n2W3mYNcw5eLNurkFLya+/Q1Mb+kGVfY5LTKeOP
         0MnkYlRqA4A853v1ZWKfgCBV7Oc01dnklNlcI=
Message-ID: <5879e51d0807251028s66178a30m9429388794633365@mail.gmail.com>
Date: Fri, 25 Jul 2008 12:28:54 -0500
From: "Gilbert B Garza" <gilbertbgarza@gmail.com>
To: couchdb-user@incubator.apache.org
Subject: Re: Renaming document attributes
In-Reply-To: <13ae4dd50807231241i693609c8j98c74f15a667de5a@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_119217_18491763.1217006934973"
References: <13ae4dd50807230926o10854c59s2436543ca36ace65@mail.gmail.com>
	 <6dfc41e10807231140j1b5a7d45ideafdf042ce14571@mail.gmail.com>
	 <13ae4dd50807231241i693609c8j98c74f15a667de5a@mail.gmail.com>

------=_Part_119217_18491763.1217006934973
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On Wed, Jul 23, 2008 at 2:41 PM, Paul Carey <paul.p.carey@gmail.com> wrote:

>
> I guess I was thinking along the lines of what to do if, say, hundreds
> of thousands of documents contained an attribute to be renamed.
> Copying the old attribute to the new one and saving would certainly
> work, but this would presumably take some time, during which views
> that referenced the attribute might return inconsistent data. At some
> point all views that reference the old attribute would need to be
> updated with the new attribute name.
>
> As I say, I have no need for this myself, at least not now. My
> question was mostly motivated by curiosity.
>
> Paul
>

You could copy all the old attribute values into the new renamed attribute,
save all the documents, and read it from the database that way. If you're
concerned about disk space after that, you can start deleting the old
attribute from all the documents without worrying about data inconsistency.

------=_Part_119217_18491763.1217006934973--