Technically, yes, you can put 17000 items in a list.For usability, no,you
can't put 17000 items in a list.
No one would want to use a lists like that, scrolling through 17000 items.
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post
Since data size is an issue, you might just returning all the record _id
fields and as you move back and forth, just query that one record and
populate. If you have 17000 items at 8 bytes (largest storage for int size
in SQLite), you would still only be looking at 136k worth of data. Most
There is a limit of 256KB (?) for your data for SQLite to be able to
move backwards at a reasonable pace. Once you go over it, you will
see a bunch of messages in the log and the move will become very slow
and AFAIK, there is nothing you can do about it other than to optimize
the size of your
you won't be cramming these 17000 records into a list anyhow. Simply limit
your SQL query accordingly so that the cursor holds no more items than you
can reasonably scroll through. If you use buttons for navigation then you
can even recreate the cursor with each button press and still be MUCH
You can cram unlimited # of items into a list. It's not like the
list keeps its entire contents around. It asks you for the data as it
needs it and it's up to the app to supply that data via whatever
means.
On Oct 6, 12:46 am, lbendlin l...@bendlin.us wrote:
you won't be cramming these 17000
5 matches
Mail list logo
