Ayende @ Rahien

Ayende Rahien commented on Designing a document database: Views

Fri, 13 Mar 2009 17:20:04 GMT

Ryan, I am actually looking for someone to sponsor the development of this :-)

Ayende Rahien commented on Designing a document database: Views

Fri, 13 Mar 2009 17:18:44 GMT

configurator, But that syntax is just ugly

huey commented on Designing a document database: Views

Fri, 13 Mar 2009 13:43:13 GMT

This is an interesting series, and now I finally grasp what its all about :) I have been reading about azure storage tables and one of the ideas is partitions -- queries over a single partition are fast, queries over multiple partitions are slow. The problem is that a partition that optimizes a query over one property might suck for a query over a different property. A solution would be to replicate the the data (or reference to) with different partitions optimized per property you want to query on. I have no idea if this is optimal (hoping some good good use practices for azure storage are shown at MIX). The problem is if you want to add a property or new query or even insert new data these multiple partitions can be out of sync easily. Seeing this post about views finally makes it all click. This is very interesting stuff with regards to scaling.

Ryan Roberts commented on Designing a document database: Views

Fri, 13 Mar 2009 11:39:33 GMT

This is a fascinating series of articles Oren, thankyou. I have a similar requirement to document database views coming up in my current work. We need view support for a system built on top of db4o to support various reporting scenarios and things like incremental search in a performant way. Lucene is my toy of choice for things like this, and we are allready using it for complex queries. It will be great to see how you tackle your query language / criteria for this. And tuples can't come soon enough for me.

Haxen commented on Designing a document database: Views

Fri, 13 Mar 2009 09:28:17 GMT

First, I like this series of posts! This that you are trying to accomplish reminds me a lot of Lotus Notes which doesn't bring back good memories. ;-)

configurator commented on Designing a document database: Views

Fri, 13 Mar 2009 02:23:37 GMT

Another option is to use some sort of duck typing for your docs For that query, all docs must support a certain interface (with Type, Title and Version as properties). I.e. it is possible to create an interface for your DDB where it is queried as such: DDB.GetDocumentsAs

configurator commented on Designing a document database: Views

Fri, 13 Mar 2009 01:50:44 GMT

Ayende, for C# 3 wouldn't a Dictionaryish syntax be best doc["Type"], doc["Title"], doc["Version"] The disadvantage with this syntax is that it is not strongly typed - but neither is the dynamic syntax.

Ayende Rahien commented on Designing a document database: Views

Fri, 13 Mar 2009 01:45:39 GMT

Configurator, Exactly!

Ayende Rahien commented on Designing a document database: Views

Fri, 13 Mar 2009 01:36:37 GMT

Rafal, when it is built, probably views aren't a good idea on top of RDBMS. the view generation tend to take a lot of time in many scenarios. Remember that the data itself is schema less, so a lot of the RDBBMS advantages are just not there. Ben, Wait for it... I think that I have better solution than the javascript in couch. Yug, You don't see where updating the views happens because I haven't discussed it yet, wait for it...

Ayende Rahien commented on Designing a document database: Views

Fri, 13 Mar 2009 01:28:50 GMT

Mike, strong type sucks

configurator commented on Designing a document database: Views

Fri, 13 Mar 2009 00:07:50 GMT

meisinger: Perhaps dynamic is necessary, because the documents are untyped and you are accessing their properties (Type, Title, Version)?

josh commented on Designing a document database: Views

Thu, 12 Mar 2009 21:37:39 GMT

@Rafal, i think you'd have to be concerned about changes to a document's title in the doc db if that view was stored in an RDBMS.

yug commented on Designing a document database: Views

Thu, 12 Mar 2009 21:00:20 GMT

Fascinating series... Thank you for sharing. It's not clear to me (from this post) where the updating of the view indexes are happening?

Ben Smith commented on Designing a document database: Views

Thu, 12 Mar 2009 20:35:47 GMT

Have you considered using a map/reduce style for defining views as per CouchDB ( [http://couchdb.apache.org/](http://couchdb.apache.org/))? The view quering language used there is JavaScript and documents are stored as JSON as you're suggesting

meisinger commented on Designing a document database: Views

Thu, 12 Mar 2009 20:19:10 GMT

great series... one question, however, why would you have to wait until C# 4.0? what are they doing to the CLR or to the code base that would allow for this to happen? i guess the bigger question really would be... why would you have to wait for anything to be able to execute that kind of code? wouldn't the view be "updated" anytime that a document was persisted? and if so wouldn't the information needed to update the view already be in the context that you are working in? or is the issue that the document db doesn't know how to update the view i am starting to loose my mind LOL

Rafal commented on Designing a document database: Views

Thu, 12 Mar 2009 20:09:10 GMT

And BTW, aren't views a good candidate to be based on RDBMS? It would save you implementation of joins, sorting, query capabilities... performance shouldn't be a problem since they could be optimized for querying.

Rafal commented on Designing a document database: Views

Thu, 12 Mar 2009 20:04:56 GMT

Ok, now I see I want it. Are you going to release it open-sourcely?