Android SQLite insert unique?

You should make use of the DatabaseUtils stringForQuery() static method that is already in Android SDK to easily retrieve a value, this example is for String bot there is also method for Long stringForQuery(SQLiteDatabase db, String query, String selectionArgs) Utility method to run the query on the db and return the value in the first column of the first row Something like String myString=DatabaseUtils. StringForQuery(getDB(),query,selectionArgs) This example was to get a string value, but you can easily adapt to get a Long value, and your query should be something like select count(*) from mytable where field1='stringtocheckagainst if this returns a number greater the zero, then the field already exists in the database Also look into code for handling orientation changes.

You should make use of the DatabaseUtils.stringForQuery() static method that is already in Android SDK to easily retrieve a value, this example is for String bot there is also method for Long stringForQuery(SQLiteDatabase db, String query, String selectionArgs) Utility method to run the query on the db and return the value in the first column of the first row. Something like String myString=DatabaseUtils. StringForQuery(getDB(),query,selectionArgs); This example was to get a string value, but you can easily adapt to get a Long value, and your query should be something like select count(*) from mytable where field1='stringtocheckagainst' if this returns a number greater the zero, then the field already exists in the database.

Also look into code for handling orientation changes.

SQLite has an INSERT OR REPLACE command (REPLACE for short, or use SQLiteDatabase.replace()) that can do what you want. However I'd suggest that your application shouldn't be re-inserting into the database every time your Activity is created unless it really needs to, so you might want to look into changing the design.

One thing is you need to handle your orientation change issue, to access db on every orientation change consumes a lot. Second thing, regarding the check duplicate record problem, you can define the column as unique like create table table_name(column_definition, unique(column_names) on conflict replace); then you can perform insert as usual, the db would ensure no duplicate.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.