<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: The case of ActiveRecord vs. CouchDB</title>
	<atom:link href="http://upstre.am/2009/03/31/the-case-of-activerecord-vs-couchdb/feed/" rel="self" type="application/rss+xml" />
	<link>http://upstre.am/2009/03/31/the-case-of-activerecord-vs-couchdb/</link>
	<description></description>
	<lastBuildDate>Mon, 08 Mar 2010 18:21:09 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Relaxing on the Couch &#124; automagically</title>
		<link>http://upstre.am/2009/03/31/the-case-of-activerecord-vs-couchdb/comment-page-1/#comment-54211</link>
		<dc:creator>Relaxing on the Couch &#124; automagically</dc:creator>
		<pubDate>Sat, 13 Jun 2009 14:53:33 +0000</pubDate>
		<guid isPermaLink="false">http://upstream-berlin.com/?p=567#comment-54211</guid>
		<description>[...] one-click CouchDB package for the Mac CouchDB: Perform like a pr0n star The case of ActiveRecord vs. CouchDB CouchDB introduction PDF CouchDB and Me CouchDB website CouchDB: The Definitive Guide CouchDB: [...]</description>
		<content:encoded><![CDATA[<p>[...] one-click CouchDB package for the Mac CouchDB: Perform like a pr0n star The case of ActiveRecord vs. CouchDB CouchDB introduction PDF CouchDB and Me CouchDB website CouchDB: The Definitive Guide CouchDB: [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alexander Lang</title>
		<link>http://upstre.am/2009/03/31/the-case-of-activerecord-vs-couchdb/comment-page-1/#comment-53134</link>
		<dc:creator>Alexander Lang</dc:creator>
		<pubDate>Thu, 28 May 2009 00:04:32 +0000</pubDate>
		<guid isPermaLink="false">http://upstream-berlin.com/?p=567#comment-53134</guid>
		<description>well, nesting things in a document is the easiest way to do something, so if what you want to do allows that i&#039;d do that first.</description>
		<content:encoded><![CDATA[<p>well, nesting things in a document is the easiest way to do something, so if what you want to do allows that i&#8217;d do that first.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PB</title>
		<link>http://upstre.am/2009/03/31/the-case-of-activerecord-vs-couchdb/comment-page-1/#comment-53083</link>
		<dc:creator>PB</dc:creator>
		<pubDate>Wed, 27 May 2009 07:10:56 +0000</pubDate>
		<guid isPermaLink="false">http://upstream-berlin.com/?p=567#comment-53083</guid>
		<description>well I don&#039;t understand the advantage nested documents would provide but I&#039;ll look into it and report back. Or whoever is faster can add the new wisdom here. I&#039;d be very interested.</description>
		<content:encoded><![CDATA[<p>well I don&#8217;t understand the advantage nested documents would provide but I&#8217;ll look into it and report back. Or whoever is faster can add the new wisdom here. I&#8217;d be very interested.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Comiezo a ver Apache CouchDB &#171; Feedverse</title>
		<link>http://upstre.am/2009/03/31/the-case-of-activerecord-vs-couchdb/comment-page-1/#comment-50132</link>
		<dc:creator>Comiezo a ver Apache CouchDB &#171; Feedverse</dc:creator>
		<pubDate>Thu, 16 Apr 2009 23:53:53 +0000</pubDate>
		<guid isPermaLink="false">http://upstream-berlin.com/?p=567#comment-50132</guid>
		<description>[...] The case of ActiveRecord vs. CouchDB [...]</description>
		<content:encoded><![CDATA[<p>[...] The case of ActiveRecord vs. CouchDB [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alexander Lang</title>
		<link>http://upstre.am/2009/03/31/the-case-of-activerecord-vs-couchdb/comment-page-1/#comment-49787</link>
		<dc:creator>Alexander Lang</dc:creator>
		<pubDate>Sun, 12 Apr 2009 12:39:14 +0000</pubDate>
		<guid isPermaLink="false">http://upstream-berlin.com/?p=567#comment-49787</guid>
		<description>well, i don&#039;t know too much about rdbms views but from what i know they are sort of what activerecord simluated with named sopes, e.g. sql queries that you put in the database and that you can run additional queries on. hence, what they do is the same a sql query would do. (correct me if i&#039;m wrong).

i&#039;d say the only thing sql and couch views have in common is that they return table data.  and here are a few of the differences:

1. couch views are the only way to get data out of couch while sql views are just a shortcut  for &quot;normal&quot; queries

2. couch views generate indexes, not tables that you can again query

3. couch views are built using map/reduce functions (with javascript, an imperative language) while sql views are built by a sql query (no idea if sql views are also precomputed?)

4. sql views work on table data. you can join and aggregate the fields of these tables. couch views work on documents (i.e. structures, potentially complex data). you don&#039;t access your data on a attribute/column level but have access to the anything you want, i.e. the average number of letters in that array of values

5. not sure about sql views but with couch views you can generate multiple entries in your result set from a single document by issuing multiple emit() calls per document

...</description>
		<content:encoded><![CDATA[<p>well, i don&#8217;t know too much about rdbms views but from what i know they are sort of what activerecord simluated with named sopes, e.g. sql queries that you put in the database and that you can run additional queries on. hence, what they do is the same a sql query would do. (correct me if i&#8217;m wrong).</p>
<p>i&#8217;d say the only thing sql and couch views have in common is that they return table data.  and here are a few of the differences:</p>
<p>1. couch views are the only way to get data out of couch while sql views are just a shortcut  for &#8220;normal&#8221; queries</p>
<p>2. couch views generate indexes, not tables that you can again query</p>
<p>3. couch views are built using map/reduce functions (with javascript, an imperative language) while sql views are built by a sql query (no idea if sql views are also precomputed?)</p>
<p>4. sql views work on table data. you can join and aggregate the fields of these tables. couch views work on documents (i.e. structures, potentially complex data). you don&#8217;t access your data on a attribute/column level but have access to the anything you want, i.e. the average number of letters in that array of values</p>
<p>5. not sure about sql views but with couch views you can generate multiple entries in your result set from a single document by issuing multiple emit() calls per document</p>
<p>&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James</title>
		<link>http://upstre.am/2009/03/31/the-case-of-activerecord-vs-couchdb/comment-page-1/#comment-49659</link>
		<dc:creator>James</dc:creator>
		<pubDate>Fri, 10 Apr 2009 20:17:11 +0000</pubDate>
		<guid isPermaLink="false">http://upstream-berlin.com/?p=567#comment-49659</guid>
		<description>I&#039;ll not speak of the specifics of ActiveRecord/Ruby, but I don&#039;t see how couchd views aren&#039;t almost exactly what views are in RDBMSes.  They filter and aggregate and return a set of &#039;documents&#039; from a set of tables.</description>
		<content:encoded><![CDATA[<p>I&#8217;ll not speak of the specifics of ActiveRecord/Ruby, but I don&#8217;t see how couchd views aren&#8217;t almost exactly what views are in RDBMSes.  They filter and aggregate and return a set of &#8216;documents&#8217; from a set of tables.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: A little place of calm &#187; Blog Archive &#187; CouchDB and data storage</title>
		<link>http://upstre.am/2009/03/31/the-case-of-activerecord-vs-couchdb/comment-page-1/#comment-49641</link>
		<dc:creator>A little place of calm &#187; Blog Archive &#187; CouchDB and data storage</dc:creator>
		<pubDate>Fri, 10 Apr 2009 13:12:18 +0000</pubDate>
		<guid isPermaLink="false">http://upstream-berlin.com/?p=567#comment-49641</guid>
		<description>[...] Alexander Lang has written a nice article about why CouchDB is not compatible with ActiveRecord, and why you should not try to coerce CouchDB into some kind of library that mimics ActiveRecord. It really is a very different thing altogether. Read: The case of ActiveRecord vs. CouchDB [...]</description>
		<content:encoded><![CDATA[<p>[...] Alexander Lang has written a nice article about why CouchDB is not compatible with ActiveRecord, and why you should not try to coerce CouchDB into some kind of library that mimics ActiveRecord. It really is a very different thing altogether. Read: The case of ActiveRecord vs. CouchDB [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alexander Lang</title>
		<link>http://upstre.am/2009/03/31/the-case-of-activerecord-vs-couchdb/comment-page-1/#comment-49363</link>
		<dc:creator>Alexander Lang</dc:creator>
		<pubDate>Tue, 07 Apr 2009 07:57:37 +0000</pubDate>
		<guid isPermaLink="false">http://upstream-berlin.com/?p=567#comment-49363</guid>
		<description>two interesting reads that add to the topic: http://debasishg.blogspot.com/2009/04/framework-inertia-couchdb-and-case-of.html (talking about developers being trapped in convenience) and http://www.cmlenz.net/archives/2007/10/couchdb-joins (3 ways to model/retrieve what AR knows as a has_many relationship)</description>
		<content:encoded><![CDATA[<p>two interesting reads that add to the topic: <a href="http://debasishg.blogspot.com/2009/04/framework-inertia-couchdb-and-case-of.html" rel="nofollow">http://debasishg.blogspot.com/2009/04/framework-inertia-couchdb-and-case-of.html</a> (talking about developers being trapped in convenience) and <a href="http://www.cmlenz.net/archives/2007/10/couchdb-joins" rel="nofollow">http://www.cmlenz.net/archives/2007/10/couchdb-joins</a> (3 ways to model/retrieve what AR knows as a has_many relationship)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Caindo do Divã (CouchDB) &#171; Codemountain</title>
		<link>http://upstre.am/2009/03/31/the-case-of-activerecord-vs-couchdb/comment-page-1/#comment-49334</link>
		<dc:creator>Caindo do Divã (CouchDB) &#171; Codemountain</dc:creator>
		<pubDate>Tue, 07 Apr 2009 00:41:09 +0000</pubDate>
		<guid isPermaLink="false">http://upstream-berlin.com/?p=567#comment-49334</guid>
		<description>[...] Ghosh também estão engajados em temas desse tipo, e aqui você pode ver uma palavrinha dos dois neste post - super atual, por sinal - do Alexander [...]</description>
		<content:encoded><![CDATA[<p>[...] Ghosh também estão engajados em temas desse tipo, e aqui você pode ver uma palavrinha dos dois neste post &#8211; super atual, por sinal &#8211; do Alexander [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: langalex</title>
		<link>http://upstre.am/2009/03/31/the-case-of-activerecord-vs-couchdb/comment-page-1/#comment-49228</link>
		<dc:creator>langalex</dc:creator>
		<pubDate>Sat, 04 Apr 2009 16:04:23 +0000</pubDate>
		<guid isPermaLink="false">http://upstream-berlin.com/?p=567#comment-49228</guid>
		<description>well I don&#039;t understand the advantage nested documents would provide but I&#039;ll look into it and report back. Or whoever is faster can add the new wisdom here. I&#039;d be very interested.</description>
		<content:encoded><![CDATA[<p>well I don&#8217;t understand the advantage nested documents would provide but I&#8217;ll look into it and report back. Or whoever is faster can add the new wisdom here. I&#8217;d be very interested.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
