Databases
StackOverflow2013
Postsdbo
POCan't open database with SQLiteAssetHelper
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POCan't open database with SQLiteAssetHelper
    text
    copied!<blockquote> <p><strong>Possible Duplicate:</strong><br> <a href="https://stackoverflow.com/questions/7316191/android-sqlite-returned-error-code-14">Android sqlite returned: error code = 14</a> </p> </blockquote> <p>I have used SQLiteAssetHelper class/library to manipulate a database from assets/databases folder like indicated in that <a href="https://github.com/jgilfelt/android-sqlite-asset-helper" rel="nofollow noreferrer">link</a>. I did exactly all the instructions, but i still can't access to the database.</p> <pre><code>09-27 19:35:46.417: I/Database(27474): sqlite returned: error code = 14, msg = cannot open file at source line 25467 09-27 19:35:46.417: E/Database(27474): sqlite3_open_v2("/data/data/com.gatec.douaa/databases/data", &amp;handle, 2, NULL) failed 09-27 19:35:46.428: W/SQLiteAssetHelper(27474): could not open database data - unable to open database file 09-27 19:35:46.428: W/SQLiteAssetHelper(27474): copying database from assets... 09-27 19:35:46.447: W/SQLiteAssetHelper(27474): extracting file: 'database.db'... 09-27 19:35:46.477: E/SQLiteAssetHelper(27474): Couldn't open data for writing (will try read-only): 09-27 19:35:46.477: E/SQLiteAssetHelper(27474): com.readystatesoftware.sqliteasset.SQLiteAssetException: Missing databases/data.zip file in assets or target folder not writable </code></pre> <p>Code:</p> <pre><code>public class MyDatabase extends SQLiteAssetHelper { private static final String DATABASE_NAME = "data"; private static final int DATABASE_VERSION = 1; public MyDatabase(Context context) { super(context, DATABASE_NAME, null, DATABASE_VERSION); } </code></pre> <p>Any help please? Don't know the source of the problem.</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

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