Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I don't know the contents of your <code>ArrayAdapter</code> or the <code>List</code> backing it but what about making the data backing the list serializable, saving it, and then loading it when the view is recreated?</p> <p>Traditionally I've seen this appraoch used when you're trying to store data when the app is being closed or risks being killed from remaining in the background. There is a great <a href="https://stackoverflow.com/questions/4393889/how-can-i-store-an-arraylist-of-custom-objects">post on serialization</a> complete with sample code here. They walk through taking an <code>ArrayList</code> of custom objects, writing it to a file and reopening it later. I think if you implemented this approach, writing the data of your backing <code>List</code> or <code>ArrayAdapter</code> in <code>onPause()</code> before the activity is destroyed, you could then reload that file when the activtivy is recreated. </p> <p>Other approaches (a/k/a backup plans):</p> <p>(1) Easy but sloppy - If your list is some primative, like a list of strings, you could always consider writing the values individually to <code>SharedPreferences</code> and reclaiming them on reload. Just be sure to assign some unique id in the storing process. </p> <p><strong>NOTE</strong> while this may work, <code>SharedPreferecnes</code> is generally not designed to handle large amounts of data so if you're list is long I would avoid this approach. For a few data points, however, I can't see it being a problem.</p> <p>(2) Slightly harder but risky - If you're <code>List</code> backing the adapter contains objects that implement <code>parcelable</code> or are already serializable, consider passing the <code>List</code> via an <code>Intent</code> to an existing activity that is in the background and using a callback to retrieve that data when the activity is recreated. This is similar to your idea of creating a background <code>Fragment</code>. Both approaches run the risk that the <code>Activity</code> or <code>Fragment</code> you are targeting will not be there. </p>
    singulars
    1. This table or related slice is empty.
    1. POGood solution to retain listview items when user rotate phone and keep all data in ArrayAdapter
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USRarw
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTDownMod
    1. COWhy use SharedPreferences when you have the onSaveInstanceState method ? As for passing the data to another part of the application - messy and ultimately unhelpful if Android destroys the application to recover memory if it is in the background. Understand the Activity and Fragment lifecycle and work with it.
      singulars
      1. PO
      1. USPhil
    2. COYea I don't think its a good idea and certainly savedInstanceState is better. But if you just had to store a couple of strings for a short time, its just a fast way to do it.
      singulars
      1. PO
      1. USRarw
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload