Description Alexander Kläser 2015-02-20 13:30:11 CET

The modifications introduced by this bug seems to have some side effects in 4.0... here is the core change:

> var _Grid = declare([EnhancedGrid], {
>     _fetch: function(start, isRender) {
>         // force start=0
>         arguments[0] = 0;
>         this.inherited(arguments);
>     },
>     ...
> }

The CSV import module in UCS@school uses a Memory store for our Grid. When scrolling, only "..." is shown beyond 30 entries. When removing the force start at 0 (see quote above), this works again, however, the double entries from Bug #25476 are back again.

When I was playing with dgrid, I noticed that I needed to introduce a Cache for caching elements that are retrieved from the moduleStore. The Cache is represented by a Memory store which is then passed to the grid. A rough sketch for the changes needed:

> postMixInProperties: function() {
>     ...
>     this._store = new Observable(new Memory({
>         idProperty: this.moduleStore.idProperty
>     }));
>     this._cache = new Cache(this.moduleStore, this._store);
> }
> ...
> filter: function(query, options) {
>     // store the last query
>     this.query = query;
>     this.standby(true);
>     this._store.setData([]);
>     this._cache.query(query, options).then(lang.hitch(this, function(result) {
>         ...
>     }
>     ...
> }

This could to the trick.

This problem occurs at all places where Memory stores (UVMM: network, drives, snapshots; System setup: Interfaces, ...) are used and that have more than 30 entries.


+++ This bug was initially created as a clone of Bug #25476 +++

Diese Query wird zweimal hintereinander ausgeführt:
{"options":{"container":"all","objectType":"groups/group","objectProperty":"name","objectPropertyValue":"*"},"flavor":"groups/group"}

Die neu "geladenen" Objekte werden durch die ersten Objekte ersetzt - siehe Screenshots.