Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>This is the way I am using at this moment... it's very complicated but at least it handles all the possible situations. In case anyone is interested.</p> <pre><code>public final class MyFragment extends Fragment { private TextView vstup; private Bundle savedState = null; @Override public View onCreateView(LayoutInflater inflater, ViewGroup container, Bundle savedInstanceState) { View v = inflater.inflate(R.layout.whatever, null); vstup = (TextView)v.findViewById(R.id.whatever); /* (...) */ /* If the Fragment was destroyed inbetween (screen rotation), we need to recover the savedState first */ /* However, if it was not, it stays in the instance from the last onDestroyView() and we don't want to overwrite it */ if(savedInstanceState != null &amp;&amp; savedState == null) { savedState = savedInstanceState.getBundle(App.STAV); } if(savedState != null) { vstup.setText(savedState.getCharSequence(App.VSTUP)); } savedState = null; return v; } @Override public void onDestroyView() { super.onDestroyView(); savedState = saveState(); /* vstup defined here for sure */ vstup = null; } private Bundle saveState() { /* called either from onDestroyView() or onSaveInstanceState() */ Bundle state = new Bundle(); state.putCharSequence(App.VSTUP, vstup.getText()); return state; } @Override public void onSaveInstanceState(Bundle outState) { super.onSaveInstanceState(outState); /* If onDestroyView() is called first, we can use the previously savedState but we can't call saveState() anymore */ /* If onSaveInstanceState() is called first, we don't have savedState, so we need to call saveState() */ /* =&gt; (?:) operator inevitable! */ outState.putBundle(App.STAV, (savedState != null) ? savedState : saveState()); } /* (...) */ } </code></pre> <p><strong>Alternatively</strong>, it is always a possibility to keep the data displayed in passive <code>View</code>s in variables and using the <code>View</code>s only for displaying them, keeping the two things in sync. I don't consider the last part very clean, though.</p>
    singulars
    1. This table or related slice is empty.
    1. POOnce for all, how to correctly save instance state of Fragments in back stack?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USMarcin Orlowski
    1. USThe Vee
    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. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTApproveEditSuggestion
    1. COThis is the best solution I've found so far but there is still one (somewhat exotic) problem remaining: if you have two fragments, `A` and `B`, where `A` is currently on the backstack and `B` is visible, then you lose the state of `A` (the invisible one) if you rotate the display _twice_. The problem is that `onCreateView()` does not get called in this scenario, only `onCreate()`. So later, in `onSaveInstanceState()` there are no views to save the state from. One would have to store and then save the state passed in `onCreate()`.
      singulars
      1. PO
      1. USdevconsole
    2. CO@devconsole I wish I could give you 5 up votes for this comment! This rotation twice thing has been killing me for days.
      singulars
      1. PO
      1. USDroidT
 

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