I have question I have read that views are indexed on disk and index may be large than the original data if it emits data from different docs type , my question Is I can’t judge in some situation that I have to use view or I have to use default get by doc name look for this scenario :
I want to make social game that will contains 3 tables as bellow :
1- UserProfile : contains all user personal info and general info like facebookID , score , coins …
2- UserDetails : it will contain all user stage saved objects like user map also UserID.
3- UserFriends : here a link table that contains only the ids of user friends and UserID .
What I did in my game is, I retrieve user profile and other user info like details by Doc Name because I am who will save them and they are countable so each user have these docs so in java I call :
client.getBuilk ( “UserProfile_UniqueID” ,”UserDetails_UniqueID” …etc ) ;
And also I can retrieve the user friends id form doc like this :
client.get( “UserFriends_UniqueID”)
Also I create view that will get just small info from the UsersProfile such as friend name and score
So after getting friends id I will call that view and support it with ComplexKeys which is friends id and all data will returns as I want .
I don’t know if this will have drawbacks and will cause problems , should I have to use views ?if yes how can I retrieve friends info for specific player?
First of all, your approach based on keys and key lookups is good. If you are happy with it you do not have to change.
Even when you are using views, at the end most of the time you use the key of the document to get the information. This is what the Java SDK is doing for example when you query a view using includeDocs=true.
Do you mind showing us an example of your JSON documents? this could help to see what could be done. But for me, based on my understanding of your model so far, you do not need views in your application.
При наиболее драматических внештатных картинах, администратор улова доставляет урегулирование, связывая с заведующим предприятия. Администратор:Воплощает публикацию по высокоэффективному и цивилизованному обслуживанию слушателей. Инструкция по охране труда администратор построению для них комфортных соглашений. Можно прочитать и тут
При наиболее драматических внештатных картинах, администратор улова доставляет урегулирование, связывая с заведующим предприятия. Администратор:Воплощает публикацию по высокоэффективному и цивилизованному обслуживанию слушателей. Инструкция по охране труда администратор построению для них комфортных соглашений. Можно прочитать и тут
well to keep his lips shut and to let the dead bury their dead.
root of your tongue, so that you cannot squeal, then I will cut you to
I heard the words and took no note, and she spoke again to Umslopogaas,
"White One, thy magic is great, and thine eyes could pierce the darkness
"I mean that–just at present, of course, he has been so upset by this
itself. By the way, if you are going up to the house, tell the cook that
"Thus, Ibubesi. Whoever drinks this medicine becomes like one dead–none
Lozelle."
But in that darkness which now and again turned to dazzling light, unlike
"I meant I was glad that they had caught my horse, not that I had to ride
unknown private reasons. The world remembers few people, even if they
bridle, led it away with the ox.
they would, could not thrust themselves free. Now hope rose in
accursed roads," and he made another grimace. "Yet I will ask
thy riddle is read for thee as the Mother of the Trees decreed that it