Why Room queries (Insert, Update, Delete, Select) in Android Kotlin? - Purpose & Use Cases

The Big Idea

Discover how Room queries save you from messy, slow data handling in your app!

The Scenario

Imagine you have a notebook where you write down your contacts. Every time you want to add, change, remove, or find a contact, you have to flip through pages manually and rewrite everything carefully.

The Problem

This manual way is slow and easy to mess up. You might lose pages, write wrong info, or spend too much time searching. It's hard to keep everything organized and up to date.

The Solution

Room queries let your app talk to a database easily. You just tell it what to add, update, delete, or find, and it does the hard work behind the scenes quickly and safely.

Before vs After

✗ Before

fun addContact(name: String, phone: String) {
  // Open file, write line, close file
}

✓ After

@Insert
suspend fun addContact(contact: ContactEntity)

What It Enables

With Room queries, your app can manage data smoothly, keeping everything accurate and fast without extra hassle.

Real Life Example

Think of a messaging app that saves your chats. Room queries help add new messages, update read status, delete old chats, and show your conversation instantly.

Key Takeaways

Manual data handling is slow and error-prone.

Room queries automate database tasks safely and efficiently.

This makes your app reliable and easy to maintain.

Practice

1. Which Room annotation is used to add a new record to the database?

easy

A. @Query

B. @Insert

C. @Delete

D. @Update

Solution

1. Step 1: Understand Room annotations for data changes

   @Insert is used to add new data, @Update modifies existing data, and @Delete removes data.

2. Step 2: Identify the annotation for adding records

   Since adding means inserting new data, @Insert is the correct annotation.

3. Final Answer:

   @Insert -> Option B

4. Quick Check:

   Add new record = @Insert [OK]

Hint: Insert means add new data, so use @Insert [OK]

Common Mistakes:

• Confusing @Update with adding new data
• Using @Delete instead of @Insert
• Thinking @Query inserts data

2. Which of the following is the correct syntax to delete a user by ID using @Query in Room?

easy

A. @Query("DELETE users WHERE id = :userId")

B. @Query("REMOVE FROM users WHERE id = :userId")

C. @Query("DELETE FROM users WHERE id = :userId")

D. @Query("DELETE * FROM users WHERE id = :userId")

Solution

1. Step 1: Recall SQL DELETE syntax

   The correct SQL command to delete rows is DELETE FROM table WHERE condition.

2. Step 2: Match correct syntax in options

   @Query("DELETE FROM users WHERE id = :userId") matches the correct SQL syntax with parameter binding (:userId).

3. Final Answer:

   @Query("DELETE FROM users WHERE id = :userId") -> Option C

4. Quick Check:

   DELETE FROM table WHERE condition = correct syntax [OK]

Hint: Use 'DELETE FROM' not 'REMOVE' or 'DELETE *' [OK]

Common Mistakes:

• Using REMOVE instead of DELETE
• Omitting FROM keyword
• Adding * after DELETE

3. Given the DAO method below, what will be the return type when calling getAllUsers()?

@Query("SELECT * FROM users")
fun getAllUsers(): List<User>

medium

A. An integer count of users

B. A single User object

C. A Boolean indicating success

D. A list of User objects

Solution

1. Step 1: Analyze the method signature

   The method returns List<User>, which means a list of User objects.

2. Step 2: Understand the SQL query

   SELECT * FROM users returns all rows, so the method returns multiple User objects in a list.

3. Final Answer:

   A list of User objects -> Option D

4. Quick Check:

   Return type List<User> means multiple users [OK]

Hint: Return type List<User> means multiple users returned [OK]

Common Mistakes:

• Thinking it returns a single User
• Confusing return type with count
• Expecting a Boolean result

4. Identify the error in this Room DAO update method:

@Update
fun updateUser(user: User): Int {
  return 1
}

medium

A. The method should not have a body; it must be abstract

B. The method should return Unit, not Int

C. The method must not have a return statement

D. The @Update annotation is missing parameters

Solution

1. Step 1: Understand Room DAO method requirements

   DAO methods with @Update must be abstract or interface methods without a body.

2. Step 2: Identify the error in the method

   This method has a body with a return statement, which is not allowed for Room DAO annotated methods.

3. Final Answer:

   The method should not have a body; it must be abstract -> Option A

4. Quick Check:

   Room DAO methods are abstract, no method body [OK]

Hint: Room DAO methods must be abstract, no method body [OK]

Common Mistakes:

• Adding method body in DAO interface
• Returning wrong types intentionally
• Missing @Update annotation

5. You want to update a user's email by their ID using Room. Which DAO method below correctly performs this update?

hard

A. @Query("UPDATE users SET email = :email WHERE id = :userId")
fun updateEmail(userId: Int, email: String)

B. @Update
fun updateEmail(userId: Int, email: String)

C. @Insert(onConflict = OnConflictStrategy.REPLACE)
fun updateEmail(userId: Int, email: String)

D. @Delete
fun updateEmail(userId: Int, email: String)

Solution

1. Step 1: Understand update options in Room

   @Update requires a full entity object, so partial updates need @Query with SQL.

2. Step 2: Check which method updates email by ID

   @Query("UPDATE users SET email = :email WHERE id = :userId") fun updateEmail(userId: Int, email: String) uses @Query with SQL UPDATE statement and parameters for userId and email, which is correct.

3. Final Answer:

   @Query("UPDATE users SET email = :email WHERE id = :userId") fun updateEmail(userId: Int, email: String) -> Option A

4. Quick Check:

   Partial update needs @Query with SQL UPDATE [OK]

Hint: Use @Query with UPDATE for partial field changes [OK]

Common Mistakes:

• Using @Update without full entity
• Using @Insert to update data
• Using @Delete for updates