Databases
StackOverflow2013
Postsdbo
POError Creating table in SQL table already exists
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POError Creating table in SQL table already exists
    primarykey
    data
    text
    <p>I have written commands to create table in <code>onCreate()</code> method of <code>DatabaseManager</code> class which extends <code>SQLiteOpenHelper</code> class. When opening database, the <code>onCreate()</code> method is being called for the first time. but still there is an error saying table corporate_boxes already exists.</p> <p>The open method</p> <pre><code>public DatabaseManager open() { ourHelper = new DatabaseManager(context); ourDatabase = ourHelper.getWritableDatabase(); return this; } </code></pre> <p>Oncreate Method</p> <pre><code>@Override public void onCreate(SQLiteDatabase db) { db.execSQL(DATABASE_CREATE_TABLE2); } </code></pre> <p><code>DATABASE_CREATE_TABLE2</code> is a string whos definition is given below,</p> <pre><code>private static final String DATABASE_CREATE_TABLE2 = "CREATE TABLE " + DATABASE_TABLE2 + " ( " + KEY_ROWID + " INTEGER PRIMARY KEY AUTOINCREMENT, " + KEY_PRODUCT + " TEXT NOT NULL, " + KEY_PRICE + " TEXT NOT NULL," + KEY_IMAGEID + " TEXT NOT NULL );"; </code></pre> <p>I also tried with <code>CREATE TABLE IF NOT EXISTS</code> but still it is giving the same error.</p> <p>Here is the stacktrace that is being displayed.</p> <pre><code>02-21 07:59:38.296: E/AndroidRuntime(1984): FATAL EXCEPTION: main 02-21 07:59:38.296: E/AndroidRuntime(1984): android.database.sqlite.SQLiteException: table corporate_boxes already exists (code 1): , while compiling: CREATE TABLE corporate_boxes ( _id INTEGER PRIMARY KEY AUTOINCREMENT, _name TEXT NOT NULL, _price TEXT NOT NULL,_imageid TEXT NOT NULL ); 02-21 07:59:38.296: E/AndroidRuntime(1984): at android.database.sqlite.SQLiteConnection.nativePrepareStatement(Native Method) 02-21 07:59:38.296: E/AndroidRuntime(1984): at android.database.sqlite.SQLiteConnection.acquirePreparedStatement(SQLiteConnection.java:882) 02-21 07:59:38.296: E/AndroidRuntime(1984): at android.database.sqlite.SQLiteConnection.prepare(SQLiteConnection.java:493) 02-21 07:59:38.296: E/AndroidRuntime(1984): at android.database.sqlite.SQLiteSession.prepare(SQLiteSession.java:588) 02-21 07:59:38.296: E/AndroidRuntime(1984): at android.database.sqlite.SQLiteProgram.&lt;init&gt;(SQLiteProgram.java:58) 02-21 07:59:38.296: E/AndroidRuntime(1984): at android.database.sqlite.SQLiteStatement.&lt;init&gt;(SQLiteStatement.java:31) 02-21 07:59:38.296: E/AndroidRuntime(1984): at android.database.sqlite.SQLiteDatabase.executeSql(SQLiteDatabase.java:1663) 02-21 07:59:38.296: E/AndroidRuntime(1984): at android.database.sqlite.SQLiteDatabase.execSQL(SQLiteDatabase.java:1594) 02-21 07:59:38.296: E/AndroidRuntime(1984): at appistic.services.tricouschocolates.categories.DatabaseManager.onCreate(DatabaseManager.java:199) 02-21 07:59:38.296: E/AndroidRuntime(1984): at android.database.sqlite.SQLiteOpenHelper.getDatabaseLocked(SQLiteOpenHelper.java:252) 02-21 07:59:38.296: E/AndroidRuntime(1984): at android.database.sqlite.SQLiteOpenHelper.getWritableDatabase(SQLiteOpenHelper.java:164) 02-21 07:59:38.296: E/AndroidRuntime(1984): at appistic.services.tricouschocolates.categories.DatabaseManager.open(DatabaseManager.java:116) 02-21 07:59:38.296: E/AndroidRuntime(1984): at appistic.services.tricouschocolates.Products.onItemSelected(Products.java:51) 02-21 07:59:38.296: E/AndroidRuntime(1984): at android.widget.AdapterView.fireOnSelected(AdapterView.java:892) 02-21 07:59:38.296: E/AndroidRuntime(1984): at android.widget.AdapterView.access$200(AdapterView.java:49) 02-21 07:59:38.296: E/AndroidRuntime(1984): at android.widget.AdapterView$SelectionNotifier.run(AdapterView.java:860) 02-21 07:59:38.296: E/AndroidRuntime(1984): at android.os.Handler.handleCallback(Handler.java:725) 02-21 07:59:38.296: E/AndroidRuntime(1984): at android.os.Handler.dispatchMessage(Handler.java:92) 02-21 07:59:38.296: E/AndroidRuntime(1984): at android.os.Looper.loop(Looper.java:137) 02-21 07:59:38.296: E/AndroidRuntime(1984): at android.app.ActivityThread.main(ActivityThread.java:5039) 02-21 07:59:38.296: E/AndroidRuntime(1984): at java.lang.reflect.Method.invokeNative(Native Method) 02-21 07:59:38.296: E/AndroidRuntime(1984): at java.lang.reflect.Method.invoke(Method.java:511) 02-21 07:59:38.296: E/AndroidRuntime(1984): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:793) 02-21 07:59:38.296: E/AndroidRuntime(1984): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:560) 02-21 07:59:38.296: E/AndroidRuntime(1984): at dalvik.system.NativeStart.main(Native Method) </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USGeros
    1. USMustafa Baquari
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POError Creating table in SQL table already exists
      1. This table or related slice is empty.
      1. VTApproveEditSuggestion
    1. COJust a wild guess since the error does not make sense when you use CREATE TABLE IF NOT EXISTS: try to remove the trailing `;` from your create statement.
      singulars
      1. POError Creating table in SQL table already exists
      1. USHenry
 

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