Conditional expressions in DynamoDB

Introduction

Conditional expressions help you check if certain conditions are true before changing data in your database. This keeps your data safe and accurate.

You want to add a new item only if it does not already exist.

You want to update a value only if it matches a specific current value.

You want to delete an item only if it meets certain criteria.

You want to avoid overwriting data accidentally.

You want to make sure a number is within a range before updating it.

Syntax

DynamoDB

ConditionExpression = "attribute_exists(attributeName) AND attribute_not_exists(otherAttribute)"

# Use placeholders for attribute names and values:
ExpressionAttributeNames = {"#attr": "attributeName"}
ExpressionAttributeValues = {":val": value}

Use ConditionExpression to write your condition.

Use placeholders like #attr and :val to avoid conflicts with reserved words.

Examples

Only add a new item if the UserID does not exist yet.

DynamoDB

ConditionExpression = "attribute_not_exists(UserID)"

Update only if Age is 18 or older.

DynamoDB

ConditionExpression = "Age >= :minAge",
ExpressionAttributeValues = {":minAge": {"N": "18"}}

Update only if Status is currently 'Pending'.

DynamoDB

ConditionExpression = "#status = :currentStatus",
ExpressionAttributeNames = {"#status": "Status"},
ExpressionAttributeValues = {":currentStatus": {"S": "Pending"}}

Sample Program

This code adds a new user to the 'Users' table only if the UserID 'user123' is not already there. If the UserID exists, it will not add and will raise an error.

DynamoDB

import boto3

# Connect to DynamoDB
client = boto3.client('dynamodb')

table_name = 'Users'

# Try to add a new user only if UserID does not exist
response = client.put_item(
    TableName=table_name,
    Item={
        'UserID': {'S': 'user123'},
        'Name': {'S': 'Alice'},
        'Age': {'N': '30'}
    },
    ConditionExpression='attribute_not_exists(UserID)'
)

print('User added successfully')

Important Notes

If the condition is false, DynamoDB returns a ConditionalCheckFailedException.

Always use condition expressions to avoid accidental data loss.

Summary

Conditional expressions let you control when data changes happen.

They help keep your data safe and consistent.

Use placeholders to avoid conflicts with reserved words.

Practice

1. What is the main purpose of using ConditionExpression in a DynamoDB operation?

easy

A. To create a new table automatically

B. To speed up the query execution

C. To ensure the operation only happens if certain conditions are met

D. To backup data before updating

Solution

1. Step 1: Understand what ConditionExpression does

   ConditionExpression is used to specify rules that must be true for the operation to proceed.

2. Step 2: Identify the purpose in data safety

   This helps prevent unwanted changes by checking conditions before updating or deleting.

3. Final Answer:

   To ensure the operation only happens if certain conditions are met -> Option C

4. Quick Check:

   ConditionExpression controls operation execution [OK]

Hint: ConditionExpression controls when changes happen [OK]

Common Mistakes:

• Thinking it speeds up queries
• Confusing with table creation
• Assuming it backs up data

2. Which of the following is the correct syntax to use a conditional expression that checks if attribute status equals active in a DynamoDB update?

easy

A. ConditionExpression: "status = 'active'"

B. ConditionExpression: "status != 'active'"

C. ConditionExpression: "status == active"

D. ConditionExpression: "#s = :active" with ExpressionAttributeNames and ExpressionAttributeValues

Solution

1. Step 1: Recognize reserved word handling

   Since status can be a reserved word, use placeholders like #s and :active.

2. Step 2: Correct syntax for equality check

   The expression must use single equals = and placeholders, not direct attribute names or double equals.

3. Final Answer:

   ConditionExpression: "#s = :active" with ExpressionAttributeNames and ExpressionAttributeValues -> Option D

4. Quick Check:

   Use placeholders for reserved words [OK]

Hint: Use placeholders (#, :) for reserved words in conditions [OK]

Common Mistakes:

• Using double equals (==) instead of single equals (=)
• Not using placeholders for reserved words
• Using wrong inequality operator

3. Given this DynamoDB update command snippet:

UpdateExpression: "SET #qty = :newQty"
ConditionExpression: "#qty < :maxQty"
ExpressionAttributeNames: {"#qty": "quantity"}
ExpressionAttributeValues: {":newQty": 10, ":maxQty": 20}

What happens if the current quantity is 25?

medium

A. The update fails because condition is false

B. The update throws a syntax error

C. The update ignores the condition and sets quantity to 10

D. The update succeeds and sets quantity to 10

Solution

1. Step 1: Understand the condition check

   The condition requires current quantity to be less than 20 for update to proceed.

2. Step 2: Compare current quantity with maxQty

   Since current quantity is 25, which is not less than 20, the condition fails.

3. Final Answer:

   The update fails because condition is false -> Option A

4. Quick Check:

   Condition false blocks update [OK]

Hint: Update only if condition is true, else it fails [OK]

Common Mistakes:

• Assuming update ignores condition
• Thinking condition causes syntax error
• Believing update always succeeds

4. You wrote this DynamoDB update:

UpdateExpression: "SET total = :p"
ConditionExpression: "total > :min"
ExpressionAttributeValues: {":p": 100, ":min": 50}

But it returns a validation error. What is the likely cause?

medium

A. Using total directly without placeholder in ConditionExpression

B. Using incorrect operator in ConditionExpression

C. Missing ExpressionAttributeNames for reserved word total

D. Missing comma in ExpressionAttributeValues

Solution

1. Step 1: Check if total is reserved

   total is a reserved word in DynamoDB, so it must use a placeholder like #pr.

2. Step 2: Identify missing placeholder usage

   The ConditionExpression uses total directly, causing validation error.

3. Final Answer:

   Using total directly without placeholder in ConditionExpression -> Option A

4. Quick Check:

   Reserved words need placeholders [OK]

Hint: Always use placeholders for reserved words in conditions [OK]

Common Mistakes:

• Ignoring reserved word rules
• Assuming operators cause error
• Overlooking syntax in ExpressionAttributeValues

5. You want to update a user's score only if the current score is less than 100 and the status is active. Which is the correct ConditionExpression to use?

hard

A. "score < 100 AND status = 'active'" without placeholders

B. "#sc < :maxScore AND #st = :activeStatus" with ExpressionAttributeNames {"#sc": "score", "#st": "status"} and ExpressionAttributeValues {":maxScore": 100, ":activeStatus": "active"}

C. "score <= 100 OR status = 'active'" with placeholders

D. "#sc > :maxScore AND #st = :activeStatus" with placeholders

Solution

1. Step 1: Use placeholders for reserved words

   Both score and status can be reserved, so use #sc and #st.

2. Step 2: Combine conditions correctly

   Use AND to require both conditions: score less than 100 and status equals active.

3. Step 3: Use correct operators and values

   Use < for less than, and equals = for status check with placeholders for values.

4. Final Answer:

   "#sc < :maxScore AND #st = :activeStatus" with ExpressionAttributeNames {"#sc": "score", "#st": "status"} and ExpressionAttributeValues {":maxScore": 100, ":activeStatus": "active"} -> Option B

5. Quick Check:

   Use AND with placeholders for multiple conditions [OK]

Hint: Use AND and placeholders for multiple conditions [OK]

Common Mistakes:

• Using OR instead of AND
• Not using placeholders for reserved words
• Using wrong comparison operators