Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Since it looks like your problem is that the user is deleting your database, just make sure to catch exceptions when you open it (or access it ... wherever you're getting the exception):</p> <pre class="lang-java prettyprint-override"><code>try { URI uri = URI.create("file:///SDCard/Databases/database1.db"); sqliteDB = DatabaseFactory.open(myURI); Statement st = sqliteDB.createStatement( "CREATE TABLE 'Employee' ( " + "'Name' TEXT, " + "'Age' INTEGER )" ); st.prepare(); st.execute(); } catch ( DatabaseException e ) { System.out.println( e.getMessage() ); // TODO: decide if you want to create a new database here, or // alert the user if the SDCard is not available } </code></pre> <p>Note that even though it's probably unusual for a user to <strong>delete</strong> a private file that your app creates, it's perfectly normal for the SDCard to be unavailable because the device is connected to a PC via USB. So, you really should always be testing for this condition (file open error).</p> <p><a href="https://stackoverflow.com/a/9272878/119114">See this answer regarding checking for SDCard availability</a>.</p> <p>Also, <a href="http://docs.blackberry.com/en/developers/deliverables/17952/SQLite_database_files_1219778_11.jsp" rel="nofollow noreferrer">read this about SQLite db storage locations</a>, and make sure to <a href="https://stackoverflow.com/a/4451954/119114">review this answer by Michael Donohue</a> about eMMC storage.</p> <hr> <h2>Update: SQLite Corruption</h2> <p><a href="http://www.sqlite.org/howtocorrupt.html" rel="nofollow noreferrer">See this link describing the many ways SQLite databases can be corrupted</a>. It definitely sounded to me like maybe the .db file was deleted, but not the journal / wal file. If that was it, you could try deleting <code>database1*</code> programmatically before you create <code>database1.db</code>. But, your comments seem to suggest that it was something else. Perhaps you could look into the file locking failure modes, too.</p> <p>If you are desperate, you might try changing your code to use a different name (e.g. <code>database2</code>, <code>database3</code>) each time you create a new db, to make sure you're not getting artifacts from the previous db.</p>
    singulars
    1. This table or related slice is empty.
    1. POBlackberry not creating a valid sqlite database
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USNate
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POBlackberry not creating a valid sqlite database
      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. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COThanks nate, I'll have a look at those links. The problem however isn't that the database is not created, it's that the file is created incorrectly. Appears on the file system, but not a valid database file.
      singulars
      1. PO
      1. USKevin
    2. COI thought your update said that the problem is that the user is manually deleting the file after your app creates it? Did I misunderstand that part?
      singulars
      1. PO
      1. USNate
    3. COOh, sorry if I'm being confusing. I can create a db fine. If I delete it from the sdcard, then next time I run the app it does not create the db correctly.
      singulars
      1. PO
      1. USKevin
 

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