http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660Configurator, Yes, it would be a look as long as the index update trigger would touch the same document. We aren't comparing the old/new data when updating a document, and the etag is always updated. http://ayende.com/4644/ravendb-splitting-entities-across-several-documents#comment18http://ayende.com/4644/ravendb-splitting-entities-across-several-documents#comment18Sun, 03 Oct 2010 12:37:25 GMTDennis, Actually, no. You would simple make two queries. a) get recent posts b) get votes where post id is in (...) from the votes index http://ayende.com/4644/ravendb-splitting-entities-across-several-documents#comment17http://ayende.com/4644/ravendb-splitting-entities-across-several-documents#comment17Sun, 03 Oct 2010 12:35:58 GMT@Ayenda: Would it be a loop even if the index result doesn't change? Suppose I define the index B = 2 * A and put a document { A = 1 } It would be changed at some point to be { A = 1, B = 2 } And then when the index is rerun it would be changed to { A = 1, B = 2 } as this is no change, the index doesn't have to be run again. Or does it? http://ayende.com/4644/ravendb-splitting-entities-across-several-documents#comment16http://ayende.com/4644/ravendb-splitting-entities-across-several-documents#comment16Fri, 01 Oct 2010 13:55:36 GMTAyende, Wouldnt that easily be a N+1 query? "Show a list of posts, and then for every post I need to add a javascript tag to see if I already votes on it, so I can get instant feedback in the gui." http://ayende.com/4644/ravendb-splitting-entities-across-several-documents#comment15http://ayende.com/4644/ravendb-splitting-entities-across-several-documents#comment15Fri, 01 Oct 2010 13:38:26 GMTDennis, I would have an additional index, that would output who voted, and I could query that index. http://ayende.com/4644/ravendb-splitting-entities-across-several-documents#comment14http://ayende.com/4644/ravendb-splitting-entities-across-several-documents#comment14Fri, 01 Oct 2010 11:25:54 GMTTorkel, No, it uses a separate document (//document id: questions/123/votes) Both documents have a Votes array http://ayende.com/4644/ravendb-splitting-entities-across-several-documents#comment13http://ayende.com/4644/ravendb-splitting-entities-across-several-documents#comment13Fri, 01 Oct 2010 11:25:24 GMTConfigurator, You can absolutely do that using an index update trigger! You just have to watch out not to modify the same document that the index is based on (other wise you create a loop). http://ayende.com/4644/ravendb-splitting-entities-across-several-documents#comment12http://ayende.com/4644/ravendb-splitting-entities-across-several-documents#comment12Fri, 01 Oct 2010 11:24:36 GMTBenny, No, it uses the votes document, not the unsplitted. http://ayende.com/4644/ravendb-splitting-entities-across-several-documents#comment11http://ayende.com/4644/ravendb-splitting-entities-across-several-documents#comment11Fri, 01 Oct 2010 11:23:45 GMT@gandjustas >>SADD is unsuitable here. You need to store Who voted. My recommendation was storing 'user ids', i.e. who's voted. Using a set also ensures you only count each users vote once. http://ayende.com/4644/ravendb-splitting-entities-across-several-documents#comment10http://ayende.com/4644/ravendb-splitting-entities-across-several-documents#comment10Thu, 30 Sep 2010 07:28:17 GMTSADD is unsuitable here. You need to store Who voted. http://ayende.com/4644/ravendb-splitting-entities-across-several-documents#comment9http://ayende.com/4644/ravendb-splitting-entities-across-several-documents#comment9Thu, 30 Sep 2010 06:34:38 GMTThis actually looks quite inefficient. If I needed to implement this in Redis I would store the user ids in 2 server-side sets, one for 'up' and the other for 'down' votes. Recording a vote can easily be done in a single 'SADD' set operation without needing to serialize/deserialize the entire document. By comparison this looks like it would be magnitudes of times slower. http://ayende.com/4644/ravendb-splitting-entities-across-several-documents#comment8http://ayende.com/4644/ravendb-splitting-entities-across-several-documents#comment8Wed, 29 Sep 2010 23:56:25 GMTHow is that better / worse than storing the votes in the Question document and having an index which projects a question with only the total votes? http://ayende.com/4644/ravendb-splitting-entities-across-several-documents#comment7http://ayende.com/4644/ravendb-splitting-entities-across-several-documents#comment7Wed, 29 Sep 2010 18:01:44 GMTI am surprised you put all the votes in one document still. In the same situation, I had stored each vote as a document then used a map/reduce index to count the totals. How would you check if someone already voted? I suppose you can create an index to split out the individual votes, so they can be read one at a time. As people vote, you're going to have concurrency issues that you wouldn't have if the votes are individual documents. http://ayende.com/4644/ravendb-splitting-entities-across-several-documents#comment6http://ayende.com/4644/ravendb-splitting-entities-across-several-documents#comment6Wed, 29 Sep 2010 16:29:32 GMTHow will you deal with the "did I vote" on this without fetching the whole thing in? http://ayende.com/4644/ravendb-splitting-entities-across-several-documents#comment5http://ayende.com/4644/ravendb-splitting-entities-across-several-documents#comment5Wed, 29 Sep 2010 12:41:26 GMTYes, I am also a little puzzled. The index definition seems to use the original document where the Votes were part of the Question document. Was that the intent? Then why show the split? /confused http://ayende.com/4644/ravendb-splitting-entities-across-several-documents#comment4http://ayende.com/4644/ravendb-splitting-entities-across-several-documents#comment4Wed, 29 Sep 2010 12:28:15 GMTA feature I'd like to see is the indexes updating entities, i.e. { //document id: questions/123 Title: "How to handle Up/Down votes with Raven?", Content: "...", } { //document id: questions/123/votes Votes: [ { Up: true, User: "users/ayende" }, { Up: false, User: "users/oren" }, ] } Would be transformed automatically to { //document id: questions/123 Title: "How to handle Up/Down votes with Raven?", Content: "...", UpVotes: 1, DownVotes: 1 } { //document id: questions/123/votes Votes: [ { Up: true, User: "users/ayende" }, { Up: false, User: "users/oren" }, ] } And the UpVotes/DownVotes would be updated whenever the index is. Do you have such a feature? http://ayende.com/4644/ravendb-splitting-entities-across-several-documents#comment3http://ayende.com/4644/ravendb-splitting-entities-across-several-documents#comment3Wed, 29 Sep 2010 11:33:23 GMTIs it just me, or does your index use the unsplited document in this sample? http://ayende.com/4644/ravendb-splitting-entities-across-several-documents#comment2http://ayende.com/4644/ravendb-splitting-entities-across-several-documents#comment2Wed, 29 Sep 2010 10:43:13 GMTIt looks like relational tables and join in view\function\storedproc, isn't it? ;) http://ayende.com/4644/ravendb-splitting-entities-across-several-documents#comment1http://ayende.com/4644/ravendb-splitting-entities-across-several-documents#comment1Wed, 29 Sep 2010 10:42:23 GMT