﻿<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>Ayende @ Rahien</title><link>http://ayende.com</link><description>Ayende @ Rahien</description><copyright>Copyright (C) Ayende Rahien  2004 - 2021 (c) 2026</copyright><ttl>60</ttl><item><title>Ayende Rahien commented on Designing a document database: Looking at views</title><description>Nathaniel,
  
I read some about it. What seems to be missing is the concept of updatable data source.
  
That is the problem that I am trying to solve at this stage. And the main goal is to reduce the amount of work that I have to do whenever I have to update a document to a minimum.
</description><link>http://ayende.com/3910/designing-a-document-database-looking-at-views#comment6</link><guid>http://ayende.com/3910/designing-a-document-database-looking-at-views#comment6</guid><pubDate>Fri, 20 Mar 2009 11:13:55 GMT</pubDate></item><item><title>Nathaniel Neitzke commented on Designing a document database: Looking at views</title><description>Ayende,
  
This is the problem that map-reduce-merge was intended to solve, relational algebra (joins especially) in map reduce.  Sorry the link before was an ACM one, but if you google for map-reduce-merge there is a decent amount of info out there.  This is what I am working on implementing at the moment.
</description><link>http://ayende.com/3910/designing-a-document-database-looking-at-views#comment5</link><guid>http://ayende.com/3910/designing-a-document-database-looking-at-views#comment5</guid><pubDate>Tue, 17 Mar 2009 14:41:40 GMT</pubDate></item><item><title>Rafal commented on Designing a document database: Looking at views</title><description>Second thought is that such join will probably have the same cost as fetching data 'by hand' in map function... 
</description><link>http://ayende.com/3910/designing-a-document-database-looking-at-views#comment4</link><guid>http://ayende.com/3910/designing-a-document-database-looking-at-views#comment4</guid><pubDate>Tue, 17 Mar 2009 07:04:34 GMT</pubDate></item><item><title>Rafal commented on Designing a document database: Looking at views</title><description>Let's stick to the invoice db example. Suppose we have invoice documents with buyerTaxID and corporate customer database, customers identified also by Tax ID. And we have a view  Tax ID -&gt; Customer (vCustomerByTaxID) . Then, when doing mapping on invoices, we could tell the system to fetch customer data from vCustomerByTaxID, where key is in invoice's buyerTaxId field. Something like
  
select d as doc, vCustomerByTaxId.Value as customer
  
from docs
  
join vCustomerByTaxId on docs.buyerTaxId
</description><link>http://ayende.com/3910/designing-a-document-database-looking-at-views#comment3</link><guid>http://ayende.com/3910/designing-a-document-database-looking-at-views#comment3</guid><pubDate>Mon, 16 Mar 2009 19:05:09 GMT</pubDate></item><item><title>Ayende Rahien commented on Designing a document database: Looking at views</title><description>Rafal,
  
Can you give me an example please?
</description><link>http://ayende.com/3910/designing-a-document-database-looking-at-views#comment2</link><guid>http://ayende.com/3910/designing-a-document-database-looking-at-views#comment2</guid><pubDate>Mon, 16 Mar 2009 18:39:29 GMT</pubDate></item><item><title>Rafal commented on Designing a document database: Looking at views</title><description>Regarding the problem with joins, maybe there should be an option to  left-join with an already existing view by its key? Not necessarily in v 1.0.
</description><link>http://ayende.com/3910/designing-a-document-database-looking-at-views#comment1</link><guid>http://ayende.com/3910/designing-a-document-database-looking-at-views#comment1</guid><pubDate>Mon, 16 Mar 2009 18:37:04 GMT</pubDate></item></channel></rss>