Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The easiest way is to save data in <code>onPause()</code> and restore it in <code>onResume()</code>. Next question is where to store data. The are few way to do that:</p> <ol> <li><strong>Using custom application context</strong></li> </ol> <p>You can extend <code>android.app.Application</code> and register your class in your manifest file by</p> <pre><code>&lt;application android:name="your.application.class" ... </code></pre> <p>This will allow you to get singleton instance of your class by calling `Context.getApplicationContext().</p> <p>For an example you can create</p> <pre><code>public class MyContext extends Application { Bundle mySavedData = null; public void setSavedData(Bundle data){ mySavedData = data; } public Bundle getSavedData() { return mySavedData; } } </code></pre> <p>and then use it like this</p> <pre><code>@overide public void onResume(){ ... Bundle state = ((MyContext) getApplicationContext()).getSavedData(); if(state != null) { /* restore states */ } ... } @overide public void onPause(){ ... Bundle state = new Bundle(); ... /* save your data here and save it into the context or set null otherwise*/ ((MyContext) getApplicationContext()).setSavedData(state); ... } </code></pre> <ol> <li><strong>Using singleton pattern</strong></li> </ol> <p>Instead of defining context you can create singleton instance</p> <pre><code>public class MySingleton { static MySingleton instance; public static MySingleton getInstance() { if(instance == null){ instance = new MySingleton(); } return instance; } public Bundle mySavedData = null; void setSavedData(Bundle data){ mySavedData = data; } public Bundle getSavedData() { return mySavedData; } } </code></pre> <p>and you can use it </p> <pre><code>@overide public void onResume(){ ... Bundle state = MySingleton.getInstance().getSavedData(); if(state != null) { /* restore states */ } ... } @overide public void onPause(){ ... Bundle state = new Bundle(); ... /* save your data here and save it into the context or set null otherwise*/ MySingleton.getInstance().setSavedData(state); ... } </code></pre> <p>Be aware that context and singletons are destroyed if application is killed. If you want to store your data permanently than using application document folder or database if recommend but I think that isn't what you looking for.</p> <p>I hope this will help you....</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to restore activity state from onPause(onSavedInstanceState won't help)
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USXeNoN
    1. USXeNoN
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow to restore activity state from onPause(onSavedInstanceState won't help)
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COthank you...i will use your answer tomorrow and will let you know if it helps,because its 3 at night here....i think i will be reading and researching on it right now...
      singulars
      1. PO
      1. USAnkit Srivastava
    2. COi was thinking if i should call the destroy method on pressing the back button??so that onDestroy is called and hence OnSavedInstances is called and this will reduce the amount of work i will have to do...do you think this is a good idea?
      singulars
      1. PO
      1. USAnkit Srivastava
    3. COTake a look on [activity lifecycle](http://developer.android.com/reference/android/app/Activity.html). Application may be killed before `onDestroy()` is called, but at that point context and singleton are lost... So, I think that will probably do a job... You can use `onDestroy()`\ `onCreate()` combination.
      singulars
      1. PO
      1. USXeNoN
 

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