#2124: Browser data in Table Attribute Manager, avoid to load all the dataset
-------------------------------+--------------------------------------------
Reporter: zarch | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: trivial | Milestone: 7.0.0
Component: wxGUI | Version: unspecified
Keywords: vector attributes | Platform: Unspecified
Cpu: Unspecified |
-------------------------------+--------------------------------------------
I would like that the Browser data, start loading in the gui only a chunk
of the whole dataset, like the first 250 rows, and then automatically
loads another chunk of rows when I'm close to the bottom.
You can see an example of what I mean if you open the sqlite database
using sqliteman [0].
Do you think that would be feasible do the same thing with the wx?
#2124: Browser data in Table Attribute Manager, avoid to load all the dataset
-------------------------------+--------------------------------------------
Reporter: zarch | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: trivial | Milestone: 7.0.0
Component: wxGUI | Version: unspecified
Keywords: vector attributes | Platform: Unspecified
Cpu: Unspecified |
-------------------------------+--------------------------------------------
Comment(by mlennert):
Replying to [ticket:2124 zarch]:
> I would like that the Browser data, start loading in the gui only a
chunk of the whole dataset, like the first 250 rows, and then
automatically loads another chunk of rows when I'm close to the bottom.
#2124: Browser data in Table Attribute Manager, avoid to load all the dataset
-------------------------------+--------------------------------------------
Reporter: zarch | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: trivial | Milestone: 7.0.0
Component: wxGUI | Version: unspecified
Keywords: vector attributes | Platform: Unspecified
Cpu: Unspecified |
-------------------------------+--------------------------------------------
Comment(by pvanbosgeo):
+ 1
I too run quite often in problems with large data sets. The solution
suggested above would be great. An alternative could be to load X rows and
have 'next' page button to load the next X rows (in such case it would be
good to offer the extra option, through a check box perhaps, to load all
data in once and to have the option to set the number of rows to load in
each page).