Databases
StackOverflow2013
Postsdbo
POWhy use the Bundle when you can just use the Application?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWhy use the Bundle when you can just use the Application?
    primarykey
    data
    text
    <p>I'm reading this article on how to : <a href="http://www.techrepublic.com/blog/app-builder/handling-internal-variable-state-in-android-development/581" rel="nofollow">correctly retain variable state in Android</a> and I'm reminded that I've never gotten a good answer (and can't find one here) for why it's better to tussle with the Bundle (which isn't a HUGE hassle, but definitely has its limitations) rather than just always have an Application overridden in your App, and just store all your persistent data members there. Is there some leakage risk? Is there a way that the memory can be released unexpectedly? I'm just not clear on this... it SEEMS like it's a totally reliable "attic" to all the Activities, and is the perfect place to store anything that you're worried might be reset when the user turns the device or suspends the app. </p> <p>Am I wrong on this? Would love to get some clarity on what the true life cycle of the memory is in the Application.</p> <hr> <p>Based on the answers below, let me extend my question.</p> <p>Suppose I have an app that behaves differently based on an XML file that it loads at startup.</p> <p>Specifically, the app is a user-info gathering app, and depending on the XML settings it will follow an open ended variety of paths (collecting info A, but not J, and offering Survey P, followed by an optional PhotoTaking opportunity etc.)</p> <p>Ideally I don't have to store the details of this behavior path in a Bundle (god forbid) or a database (also ugly, but less so). I would load the XML, process it, and have the Application hold onto that structure, so I can refer to it for what to do next and how. If the app is paused and the Application is released, it's not *THAT big a hassle to check for null in my CustomFlow object (that is generated as per the XML) and re-instantiate it. It doesn't sound like this would happen all that often, anyway. Would this be a good example of where Application is the *best tool?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USBill the Lizard
    1. USGenia S.
    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. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POWhy use the Bundle when you can just use the Application?
      1. USlukuluku
      1. VTFavorite
    2. VO
      singulars
      1. POWhy use the Bundle when you can just use the Application?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POWhy use the Bundle when you can just use the Application?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COGiven your description I would totally agree with your edit.
      singulars
      1. POWhy use the Bundle when you can just use the Application?
      1. USFuzzical Logic
    2. COawesome, thanks!
      singulars
      1. POWhy use the Bundle when you can just use the Application?
      1. USGenia S.
    3. CONo problem. Like everyone here has emphasized, it depends on *how* it is all being used. Your example was a great one, because it takes the run-time data away from the run-time state and allows your components to initiate action based on that data, rather than events.
      singulars
      1. POWhy use the Bundle when you can just use the Application?
      1. USFuzzical Logic
 

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