Is there any limit to number of list_items that one can put and then query
using external itemsets example, lets say we have 500,000 records in a CSV
file, will that be any issue for ODK collect e.g. slow response, etc.
Is there any limit to number of list_items that one can put and then query
using external itemsets example, lets say we have 500,000 records in a CSV
file, will that be any issue for ODK collect e.g. slow response, etc.
I have around 1K records in CSV right now, no issues with that. But soon
it'll hit 10K as it automatically updates from database. I'll keep posted
here.
From our ODK Tables experience, the biggest performance factor will be
whether your filter criteria will limit the displayable set of values to a
reasonably small set of values -- e.g., a few dozen.
If your list of possible choices contains 100's of items, it is likely that
your form will be unmanageably slow to render that page, and it would
probably be impossible for a user to scroll through and use.
The filter criteria for external item sets is directly applied at the
database query layer, which should be very efficient.
In ODK Tables, for the Spreadsheet view, we determined that we could not
use the standard UI widgets for the table headers and cells shown that view
-- it became extremely slow to render. This led us to not use any UI
widgets, but to draw the raw content and tablular grid ourselves on that
page, which vastly increased performance, at the expense of some very
tricky code.
Mitch
···
On Thu, Feb 13, 2014 at 8:41 PM, Ayub wrote:
Hi Yaw,
I have around 1K records in CSV right now, no issues with that. But soon
it'll hit 10K as it automatically updates from database. I'll keep posted
here.
Thanks for the details Mitch, i will keep those in mind. Just a follow up
question, does ODK Tables uses no standard android widget/view (i.e.
TextView) for displaying data as table?
The "Spreadsheet View" of ODK Tables is implemented as a nested set of
vertical and horizontal scrolling regions with fixed top and bottom rows
and a tabular body.
The top, bottom and tabular body of that screen are all implemented
directly on top of "View" via org.opendatakit.tables.views.TabularView
···
On Mon, Feb 17, 2014 at 3:08 AM, Ayub wrote:
Thanks for the details Mitch, i will keep those in mind. Just a follow up
question, does ODK Tables uses no standard android widget/view (i.e.
TextView) for displaying data as table?