Alloy SQLite collections: paginate with limit/offset per fetch, or fetch once and slice in memory?
I'm building an Alloy screen backed by a Backbone collection using the local SQLite adapter. The table will hold several thousand rows, and the target devices have limited RAM, so I need to decide how to bound the query before wiring up data-binding. As I understand it, the collection's fetch ultimately runs SQL through the adapter, so I can pass limit/offse
sqlite