ravendb - Some guidance request on 'custom defined' resultsets -


i guidance/thoughts on route create functionality allows me let user customize datasets. have added image showing functionality has been called queues here.

a view segmentation of resultset conditions defined either system (default views) or user.

i can create predefined indexes/projections default views under control stuck on approach when user should able create custom views.

  • i can create 1 big index properties, , query fields on index in conditions defined user. in scenario index 1 big blob of information. easiest way feels ugly.
  • i can dynamically create new index, based on entered conditions. never explored options of runtime defined indexes before though.
  • i can dynamically create query conditions, have deal stale results because let ravendb define index; avoid index creation ravendb if possible.

some guidance highly appreciated; how , parts of ravendb can efficiently accomplish this? not in search of complete solution, since personal project experimenting ravendb.

enter image description here

this question might broad/generic here's 2 cents.

yes, agree 1 massive index not optimal. in many cases can creative breaking down index smaller indexes.

i don't suggest create run-time indexes based on how user using application. that's dynamic indexes for. ravendb create index , manage importance. so, have dynamic indexes don't used anymore, ravendb abandon them. if you're worried staleness, can wait non-stale results.

i'm not clear on use-case, maybe design app in such way save views (custom or default) raven documents. example, given picture attached, "unassigned issues" , "due week" 2 separate documents. allow keep small number of static indexes.


Comments

Popular posts from this blog

angularjs - ADAL JS Angular- WebAPI add a new role claim to the token -

node.js - Using Node without global install -

php - CakePHP HttpSockets send array of paramms -