Opened 6 years ago

Last modified 8 months ago

#2124 new enhancement

Browser data in Table Attribute Manager, avoid to load all the dataset

Reported by: zarch Owned by: grass-dev@…
Priority: major Milestone: 7.6.2
Component: wxGUI Version: unspecified
Keywords: vector attributes Cc:
CPU: Unspecified Platform: Unspecified

Description

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?

[0] http://sqliteman.com/

Change History (11)

comment:1 in reply to:  description Changed 6 years ago by mlennert

Replying to 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.

+1

Large datasets can be quite slow to load...

Moritz

comment:2 Changed 6 years ago 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).

comment:3 Changed 6 years ago by neteler

Priority: trivialmajor

Raising priority

comment:4 Changed 4 years ago by martinl

Milestone: 7.0.07.0.5

comment:5 Changed 3 years ago by martinl

Milestone: 7.0.57.3.0

comment:6 Changed 3 years ago by martinl

Milestone: 7.3.07.4.0

Milestone renamed

comment:7 Changed 22 months ago by neteler

Milestone: 7.4.07.4.1

Ticket retargeted after milestone closed

comment:8 Changed 18 months ago by neteler

Milestone: 7.4.17.4.2

comment:9 Changed 14 months ago by martinl

Milestone: 7.4.27.6.0

All enhancement tickets should be assigned to 7.6 milestone.

comment:10 Changed 10 months ago by martinl

Milestone: 7.6.07.6.1

Ticket retargeted after milestone closed

comment:11 Changed 8 months ago by martinl

Milestone: 7.6.17.6.2

Ticket retargeted after milestone closed

Note: See TracTickets for help on using tickets.