Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Well, There are so many problems with the code, that I think you must have a better look at SQLite structure in android, technically, <strong>Android SQLite</strong> and <strong>SQLCipher</strong> look totally the same (except for the password). so if you write an standard SQLite application, it can be changed to SQLCipher easily,</p> <p>I suggest you read this fine article about SQLite in android,</p> <p><a href="http://www.vogella.com/articles/AndroidSQLite/article.html" rel="nofollow">http://www.vogella.com/articles/AndroidSQLite/article.html</a></p> <p><strong>Tip</strong>: There is no need to call <strong>openOrCreateDatabase</strong> when you are using <strong>SQLiteOpenHelper</strong>, calling <strong>getWritableDatabase</strong> would do the job, also you must be having a <strong>SQLiteDatabase</strong> object which is taken from <strong>getWritableDatabase</strong> method, calling <strong>getWritableDatabase</strong> for every time you want to insert a record is not right.</p> <p>these parts would be removed, </p> <pre><code> // in onCreate method File file = getDatabasePath(DatabaseClass.DATABASE_NAME); file.mkdir(); file.delete(); sqldb = SQLiteDatabase.openOrCreateDatabase(file,key, null); db = new DatabaseClass(this); // in saveData method db.getWritableDatabase(key).insert("mylistdata", DatabaseClass.NAME , insertData); </code></pre> <p>Instead you must do something like this</p> <pre><code> // in onCreate method try{ sqldb = new DatabaseClass(this).getWritableDatabase(key); }catch(Throwable e){ // error occurred } // in insert action try{ sqldb.insert("tablename", null, contentValues); }catch(Throwable e){ // error occurred } </code></pre> <p>This way you can also see if an error occurred, Remember, not to use <strong>Exception</strong> class on the catch phrase, only <strong>Throwable</strong>! </p> <p>Also, I would not suggest to close the connection on every insert action, It's better to be taken care of in higher levels</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to encrypt/decrypt in SQLCipher
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USHossein Shahdoost
    1. USHossein Shahdoost
    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
    1. COI'm not sure why you are recommending to catch Throwable rather than Exception. The javadocs for the other Throwable subclass (ie Error) say that it is not reasonable to catch Errors: http://docs.oracle.com/javase/6/docs/api/java/lang/Error.html
      singulars
      1. PO
      1. USJames Baxter
    2. COWe have two kinds of Throwables, Exceptions and Errors. Sometimes SQLCipher returns Error (if any library is missing) not Exception. In order to catch that you should use Throwable on the catch statement. Even though it should be handled in multiple levels but you should always remember to write your sqlcipher commands inside a Throwable catch in order to avoid your app from crashing, http://stackoverflow.com/questions/2274102/difference-between-using-throwable-and-exception-in-a-try-catch
      singulars
      1. PO
      1. USHossein Shahdoost
 

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