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

[landam]

Reported by zarch on 1 Nov 2013 13:12 UTC 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/

Migrated-From: https://trac.osgeo.org/grass/ticket/2124

[landam]

Comment by mlennert on 4 Dec 2013 14:00 UTC 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.

+1

Large datasets can be quite slow to load...

Moritz

[landam]

Comment by pvanbosgeo on 10 Jan 2014 08:30 UTC

• 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).

[landam]

Comment by neteler on 26 Mar 2014 15:57 UTC Raising priority

[landam]

Modified by @landam on 12 May 2016 06:42 UTC

[landam]

Modified by @landam on 25 Aug 2016 15:47 UTC

[landam]

Comment by @landam on 27 Aug 2016 13:42 UTC Milestone renamed

[landam]

Comment by neteler on 26 Jan 2018 11:40 UTC Ticket retargeted after milestone closed

[landam]

Modified by neteler on 12 Jun 2018 20:48 UTC

[landam]

Comment by @landam on 25 Sep 2018 16:51 UTC All enhancement tickets should be assigned to 7.6 milestone.

[landam]

Comment by @landam on 25 Jan 2019 21:07 UTC Ticket retargeted after milestone closed