[Tickets #12353] NoSQL creates indexes for collections not used

[noreply at bugs.horde.org]

BITTE NICHT AUF DIESE NACHRICHT ANTWORTEN. NACHRICHTEN AN DIESE  
E-MAIL-ADRESSE WERDEN NICHT GELESEN.

Ticket-URL: http://bugs.horde.org/ticket/12353
------------------------------------------------------------------------------
  Ticket           | 12353
  Erstellt Von     | michael at bigmichi1.de
  Zusammenfassung  | NoSQL creates indexes for collections not used
  Warteschlange    | Horde Framework Packages
  Version          | Git master
  Typ              | Bug
  Status           | Unconfirmed
  Priorität        | 2. Medium
  Milestone        |
  Patch            |
  Zuständige       |
------------------------------------------------------------------------------


michael at bigmichi1.de (2013-06-13 12:27) hat geschrieben:

i configures horde to use mongodb as storage for cache, prefs and  
sessions. the configurationpage shows me that i need to create indices  
so i have done it. after a while i looked in the db and i saw that now  
  i have this:

  horde (7)
  - horde.horde_prefs (0)
  - horde.horde_sessionhandler (0)
  - horde_cache (5)
  - horde_prefs (3)
  - horde_sessionhandler (1)
  - system.indexes (9)
  - system.users (1)

the first two entries are created while creating the indices through  
the configuration screen and the others are created automatically by  
using horde. so the collections with indices are not filled or the  
other way around the collections that are used by horde didn't have  
the indices.

i also notices that if i set a dbname in the nosql configuration this  
value isn't shown after a saving the settings