Databases
StackOverflow2013
Postsdbo
POFiles not being written to device
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POFiles not being written to device
    primarykey
    data
    text
    <p>I have been trying a hundred different methods to solve my problem, but for some reason they simple won't work. I'm trying to make a quick and dirty way, for my application to be persistent. It basically got a lot of objects it needs to save when destroying, so I thought I would make it put the objects into an ArrayList, and then write the ArrayList to the file using an ObjectOutputStream. </p> <pre><code>public void onStop() { super.onStop(); Log.d("Event", "Stopped"); FileOutputStream fos = null; ObjectOutputStream oos = null; try { fos = openFileOutput("Flights", MODE_WORLD_WRITEABLE); oos = new ObjectOutputStream(fos); } catch (FileNotFoundException e) { e.printStackTrace(); } catch (IOException e) { e.printStackTrace(); } ArrayList&lt;Flight&gt; alFlightList = new ArrayList&lt;Flight&gt;(); Iterator it = flightMap.entrySet().iterator(); while (it.hasNext()) { Map.Entry pairs = (Map.Entry)it.next(); alFlightList.add((Flight) pairs.getValue()); } try { oos.writeObject(alFlightList); oos.close(); } catch (IOException e) { e.printStackTrace(); } finally { Log.d("Info", "File created!"); } } </code></pre> <p>I got a similar algorithm for reading it out again, but it complains about there not being any file to read from. I know using files for persistence is not the best practice, but this is as previously mentioned, supposed to have been a quick and dirty solution. (But the time I have used on it now, might as well have been spent on making a database. ._.) Thanks!</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USMartin
    1. USMartin
    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. This table or related slice is empty.
    1. COonDestroy() is not guaranteed to be called. Try putting some logging in to see when it actually is. More like you will want to move the saving to onPause() or onStop() as these are the points where an application becomes killable (depending on android version - see the activity lifecycle docs). It is also possible that in your tests onDestroy() simply hasn't happened yet since there has been no need to destroy the activity. Of course your reading algorithm should handle the case of there being nothing to restore from, since it could be a first run.
      singulars
      1. POFiles not being written to device
      1. USChris Stratton
    2. COI thought about that, and have been logging all events happening, but even though it indeed did destroy it a lot of times, it still didn't work. (Though the idea of moving it is a good idea, and is something I will do once this problem is fixed.)
      singulars
      1. POFiles not being written to device
      1. USMartin
    3. COAdd additional logging through the code above so you figure out how far it gets. Are you sure there are no errors in the log already? Also, use run-as your.package.name in the adb shell and manually check for the existence of the file.
      singulars
      1. POFiles not being written to device
      1. USChris Stratton
 

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