Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I see a problem that on your Android SQLite <code>CREATE_LOGIN_TABLE</code> statement, there is no creation of column <code>encrypted_password</code>. Then your table has only 11 columns which leads to maximum index 10. There is no column with index 11 and no column with name <code>encrypted_password</code> and calling <code>cursor.getString(11);</code> is the reason of error which force closes your application.</p> <p><strong>Problem of all your reading of database data are hard coded indexes which do not match order of created columns.</strong> When you create your table on your <code>onCreateDatabase()</code> method, column order is: </p> <ol> <li>id</li> <li>fname</li> <li>lname</li> <li>email </li> </ol> <p>etc. due to order of column names in create table statement.</p> <p>Than in your <code>getUserDetails</code> method, you are taking fname with index 5, lname with index 6 etc. hard coded indexes does not match the order of columns in create table statement and you take username and id values instead of fname and lname. Simmilar it is for other columns.</p> <p>For properly work with column indexes, you should use <code>getColumnIndex(String columnName)</code> method on <code>Cursor</code> instead of hard coded indexes. For example:</p> <pre><code>int fnameIndex = cursor.getColumnIndex(KEY_FIRSTNAME); String fname = cursor.getString(fnameIndex); </code></pre> <p>Here is snippet of code you could use in your <code>getUserDetails()</code> method:</p> <pre><code> user.put("id", cursor.getString(cursor.getColumnIndex(KEY_ID))); // id - uid user.put("username", cursor.getString(cursor.getColumnIndex(KEY_USERNAME))); // uname - username user.put("email", cursor.getString(cursor.getColumnIndex(KEY_EMAIL))); user.put("fname", cursor.getString(cursor.getColumnIndex(KEY_FIRSTNAME))); user.put("lname", cursor.getString(cursor.getColumnIndex(KEY_LASTNAME))); user.put("dob", cursor.getString(cursor.getColumnIndex(KEY_DATEOFBIRTH))); user.put("tel", cursor.getString(cursor.getColumnIndex(KEY_TELEPHONE))); user.put("address", cursor.getString(cursor.getColumnIndex(KEY_ADDRESS))); user.put("ptc", cursor.getString(cursor.getColumnIndex(KEY_CREATED_AT))); </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POAndroid, SQLITE: Failed to read row 0, column 11 from a CursorWindow which has 1 rows, 11 columns
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USJosef Raška
    1. USJosef Raška
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POAndroid, SQLITE: Failed to read row 0, column 11 from a CursorWindow which has 1 rows, 11 columns
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COI don't fully understand this, could you write me the full code of public void onCreate(SQLiteDatabase db) ? And also, without address, telephone, date of birth and post code, the account info is printed perfect with no errors, so idk about this theory for encrypted_password cause my API solves that, I added my API in the post btw
      singulars
      1. PO
      1. USSimon_says
    2. COI cannot write you onCreate method which will work because of different indexes in your code. Index is order of column creation in your on create statement so you should sync column order in your CREATE_LOGIN_TABLE statement and cursor.getString() methods. Check edit.
      singulars
      1. PO
      1. USJosef Raška
    3. COthis was the output with your code http://puu.sh/61cKT.jpg
      singulars
      1. PO
      1. USSimon_says
 

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