Hi Pete,
what you believe "... /I believe the datagrid loads only enough database
rows to fill the number of rows that are visible in the datagrid .../",
unfortunately, is incorrect ...
... to have this behavior you have to manually code a procedure, named
"GetDataForLine", which fill in the data that the data grid needs.
Please see here :
http://lessons.runrev.com/s/lessons/m/datagrid/l/7341-displaying-large-amounts-of-data
Guglielmo
On 05.03.2012 08:45, Pete wrote:
... omissis ... I did not do any coded timings but
retrieving and displaying the records in an LC datagrid took around 3-4
times longer than in sqlite3. The datagrid was using the
dgNumberOfRecords/GetDataForLine techniques outlined in the datagrid manual
and there was no data formatting involved.
The crazy thing about this is that, using those techniques,*I believe the
datagrid loads only enough database rows to fill the number of rows that
are visible in the datagrid*, adding more rows as the user scrolls. So the
comparison is really between selecting and displaying all 48,000 rows in
sqlite3 vs selecting 48,000 rows and displaying only 11 rows (the number of
rows in my datagrid).
... omissis ...
Pete
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
