向DB Helper传值时遇两处错误求助：查询及MainActivity报错

Hey there! Let’s dive into the most likely fixes for the errors you’re facing—since you mentioned a question mark-related issue in your DB Helper and another problem in MainActivity, here are targeted troubleshooting steps based on common Android SQLite pitfalls:

These almost always tie to how you’re using SQLite’s placeholder syntax (?) in your queries. Here are the top culprits:

• Mismatched placeholder and value count: If your query has 2 ? placeholders, you need to pass exactly 2 values to bind to them. For example, this will throw an error:

  // Wrong: 2 placeholders, only 1 value passed
  String query = "SELECT * FROM tasks WHERE id = ? AND status = ?";
  Cursor cursor = db.rawQuery(query, new String[]{"1"});
  

  Correct it by matching the number of values to placeholders.
• Direct value concatenation (no placeholders): If you skipped ? and inserted values directly into the query string, you’ll get syntax errors (and risk SQL injection!). Always use placeholders like this:

  // Correct approach
  String query = "INSERT INTO users (name, email) VALUES (?, ?)";
  db.execSQL(query, new Object[]{"John Doe", "john@example.com"});
  

• Incorrect value type for placeholders: When using rawQuery, all values must be passed as a String[] array. For numbers or booleans, convert them to strings first with String.valueOf().
• Typos in the SQL query: A missing comma, extra bracket, or misspelled column name can make SQLite misinterpret your ? placeholders. Double-check your query syntax against your table schema.

Since you didn’t share the exact error details, here are common issues that pop up when interacting with a DB Helper from an Activity:

• Null DB Helper instance: If you forgot to initialize your DB Helper before calling its methods, you’ll get a NullPointerException. Make sure you’re creating the helper properly:

  // Initialize in onCreate() or before using it
  MyDBHelper dbHelper = new MyDBHelper(this);
  SQLiteDatabase db = dbHelper.getReadableDatabase();
  

• Cursor leaks or unhandled nulls: Always check if a cursor is null before accessing it, and close it (and the database) in a finally block to avoid memory leaks:

  Cursor cursor = null;
  try {
      cursor = db.rawQuery(query, args);
      if (cursor.moveToFirst()) {
          // Process your data here
      }
  } finally {
      if (cursor != null) cursor.close();
      db.close();
  }
  

• Running DB operations on the main thread: Doing database work directly on the UI thread can cause ANRs (Application Not Responding) or crashes. Use Kotlin Coroutines, AsyncTask, or a background thread to handle queries.
• Invalid context when creating the DB Helper: Passing a getApplicationContext() when you need an Activity context (or vice versa) can lead to unexpected behavior. Stick to using this (the Activity instance) when initializing the helper from MainActivity.

If you can share the exact error messages from Logcat and snippets of the problematic code in your DB Helper and MainActivity, I can help you pinpoint the exact issue!

内容的提问来源于stack exchange，提问作者Zeljo