http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660schorsch, Yes, it should http://ayende.com/4535/set-based-operations-with-ravendb#comment8http://ayende.com/4535/set-based-operations-with-ravendb#comment8Fri, 11 Jun 2010 10:21:30 GMTIs there a chance that RavenDB works in MS Azure? Or do you have planned to support MS Azure as a plattform for RavenDB? http://ayende.com/4535/set-based-operations-with-ravendb#comment7http://ayende.com/4535/set-based-operations-with-ravendb#comment7Fri, 11 Jun 2010 09:23:47 GMTI think one of the primary reasons that most of the NoSQL providers dont provide set operations is because they're actually NoACID providers. What I mean here is that because for distributed scenarios we'll have varying levels of consistency, and as a result, an operation like "UPDATE a WHERE b" is bound to run into issues. You deal with this to some degree with the fact that we can have stale indicies, but for a multi-server scenario, you'd need to do one of the following: 1) always have allowStale = TRUE 2) implement some form of consistent reads. To do this you'd have to have some form of lock server (BigTable has a distributed lock server, i'm assuming SimpleDB does the same) Have you thought about the multi-server scenario much Ayende? It seems like you've focused RavenDB more on being a document DB than a distributed DB. http://ayende.com/4535/set-based-operations-with-ravendb#comment6http://ayende.com/4535/set-based-operations-with-ravendb#comment6Thu, 03 Jun 2010 16:51:10 GMTOfftopic, but do you have any plans to talk about your experiences with MEF? I was surprised when I saw you were using it in RavenDB... When I dig into the docs I feel like its just another IoC container except with different naming semantics. well and the docs feel mostly like promotional materials too much fluff. It would be good to get your take on it. http://ayende.com/4535/set-based-operations-with-ravendb#comment5http://ayende.com/4535/set-based-operations-with-ravendb#comment5Thu, 03 Jun 2010 16:15:00 GMTFixed, thanks http://ayende.com/4535/set-based-operations-with-ravendb#comment4http://ayende.com/4535/set-based-operations-with-ravendb#comment4Thu, 03 Jun 2010 10:19:52 GMTDennis, There is no such things as joins for Raven. For version = version +1, you can use Increment For id in (...), you just pass the list of ids http://ayende.com/4535/set-based-operations-with-ravendb#comment3http://ayende.com/4535/set-based-operations-with-ravendb#comment3Thu, 03 Jun 2010 10:17:21 GMTtypo in your docs: "As you can see though, the IsStale flag is still false, because in the mean time somebody else has added yet another blog entry." that should be "still TRUE" http://ayende.com/4535/set-based-operations-with-ravendb#comment2http://ayende.com/4535/set-based-operations-with-ravendb#comment2Thu, 03 Jun 2010 10:16:39 GMTVery nice, that will definitely be useful. But, those are trivial examples. What about more complex ones, e.g. where there is a join involved or "dynamic" values. e.g. a update operation like update x set version = version + 1, deleted_date = getutcdate() where id in (select xid from y) http://ayende.com/4535/set-based-operations-with-ravendb#comment1http://ayende.com/4535/set-based-operations-with-ravendb#comment1Thu, 03 Jun 2010 10:09:00 GMT