SET expression for adding/changing in DynamoDB - Step-by-Step Execution

Concept Flow - SET expression for adding/changing

Start Update Request

↓

Parse SET Expression

↓

Identify Attributes to Add or Change

↓

Apply Changes to Item

↓

Save Updated Item

↓

Return Success or Error

This flow shows how DynamoDB processes a SET expression to add or change attributes in an item during an update.

Execution Sample

DynamoDB

UpdateExpression: "SET Age = Age + :inc, City = :newCity"
ExpressionAttributeValues: {":inc": 1, ":newCity": "Seattle"}

This update adds 1 to the Age attribute and changes City to 'Seattle' in the item.

Execution Table

Step	Attribute	Current Value	Operation	Value Used	New Value
1	Age	30	Add	1	31
2	City	"New York"	Change	"Seattle"	"Seattle"
3	Save Item	N/A	N/A	N/A	Age=31, City="Seattle"
4	End	N/A	N/A	N/A	Update complete

💡 All SET operations applied; item updated successfully.

Variable Tracker

Attribute	Start	After Step 1	After Step 2	Final
Age	30	31	31	31
City	"New York"	"New York"	"Seattle"	"Seattle"

Key Moments - 2 Insights

Why does Age increase from 30 to 31 instead of being replaced?

Because the SET expression uses 'Age = Age + :inc', it adds the value 1 to the existing Age (30), resulting in 31, as shown in execution_table step 1.

What happens if the attribute does not exist before the update?

DynamoDB creates the attribute with the new value. For example, if City did not exist, it would be added with value 'Seattle' as in step 2.

Visual Quiz - 3 Questions

Look at the execution table, what is the value of Age after step 1?

A 30

B 31

C 1

D 32

💡 Hint

Check the 'New Value' column for Age at step 1 in the execution_table.

At which step does the City attribute change to 'Seattle'?

A Step 3

B Step 1

C Step 2

D Step 4

💡 Hint

Look at the 'Attribute' and 'New Value' columns in execution_table rows.

If the SET expression was only 'SET Age = :newAge' with :newAge = 35, what would be the Age after update?

A 35

B 31

C 30

D 36

💡 Hint

Replacing Age sets it directly to the new value, not adding.

Concept Snapshot

SET expression in DynamoDB UpdateItem:
- Use 'SET' to add or change attributes.
- Syntax: SET attr = value or attr = attr + value
- Adds attribute if missing, updates if exists.
- Supports arithmetic for numbers.
- Use ExpressionAttributeValues for values.

Full Transcript

This visual execution shows how DynamoDB processes a SET expression during an update. Starting with an item having Age 30 and City 'New York', the SET expression 'SET Age = Age + :inc, City = :newCity' adds 1 to Age and changes City to 'Seattle'. Step 1 adds 1 to Age, making it 31. Step 2 changes City to 'Seattle'. The updated item is saved with Age 31 and City 'Seattle'. Key points include that adding to an attribute increases its value, and missing attributes are created. The quiz checks understanding of these steps and outcomes.

Practice

1. What does the SET expression do in a DynamoDB UpdateItem operation?

easy

A. It creates a new table.

B. It adds new attributes or updates existing attributes in an item.

C. It retrieves items from the table.

D. It deletes attributes from an item.

Solution

1. Step 1: Understand the purpose of SET in UpdateItem

   The SET expression is used to add new attributes or change existing ones in a DynamoDB item.

2. Step 2: Compare with other operations

   Deleting attributes uses REMOVE, retrieving uses GetItem or Query, and creating tables uses CreateTable, not SET.

3. Final Answer:

   It adds new attributes or updates existing attributes in an item. -> Option B

4. Quick Check:

   SET expression = add or update attributes [OK]

Hint: SET means add or change attributes in DynamoDB [OK]

Common Mistakes:

• Confusing SET with REMOVE for deleting attributes
• Thinking SET retrieves data
• Assuming SET creates tables

2. Which of the following is the correct syntax for a SET expression to update an attribute named age to 30?

easy

A. SET age == 30

B. SET age := 30

C. SET age -> 30

D. SET age = 30

Solution

1. Step 1: Recall correct SET syntax

   In DynamoDB, the SET expression uses a single equals sign (=) to assign new values.

2. Step 2: Check each option

   SET age = 30 uses 'SET age = 30' which is correct. Options A, B, and D use invalid operators for assignment.

3. Final Answer:

   SET age = 30 -> Option D

4. Quick Check:

   Assignment uses = in SET expression [OK]

Hint: Use single = for assignment in SET expression [OK]

Common Mistakes:

• Using := or == instead of =
• Using arrows or other symbols
• Missing the SET keyword

3. Given the following UpdateItem call:
UpdateExpression: "SET #n = :newName, age = age + :inc",
ExpressionAttributeNames: {"#n": "name"},
ExpressionAttributeValues: {":newName": "Alice", ":inc": 1}
What will be the effect on the item?

medium

A. The attribute 'name' is set to 'Alice' and 'age' is incremented by 1.

B. The attribute 'name' is set to ':newName' and 'age' is set to ':inc'.

C. The attribute 'name' is deleted and 'age' is unchanged.

D. Syntax error due to missing commas.

Solution

1. Step 1: Understand the UpdateExpression

   The expression sets the attribute 'name' (aliased as #n) to the value ':newName' which is 'Alice'. It also increments 'age' by the value ':inc' which is 1.

2. Step 2: Confirm syntax and effect

   The syntax is correct with commas separating updates. So, 'name' becomes 'Alice' and 'age' increases by 1.

3. Final Answer:

   The attribute 'name' is set to 'Alice' and 'age' is incremented by 1. -> Option A

4. Quick Check:

   SET updates multiple attributes correctly [OK]

Hint: Commas separate multiple SET updates; placeholders map values [OK]

Common Mistakes:

• Confusing placeholders with literal strings
• Missing commas between updates
• Not using ExpressionAttributeNames for reserved words

4. Identify the error in this UpdateExpression:
SET age = age + :inc newName = :bob

medium

A. Using double quotes inside expression values.

B. Incorrect use of colon before newName.

C. Missing comma between updates.

D. Using plus sign for addition is invalid.

Solution

1. Step 1: Analyze the UpdateExpression syntax

   The expression tries to update 'age' and 'newName' but lacks a comma between the two updates.

2. Step 2: Check other syntax elements

   Placeholders (:inc, :bob) are used correctly for values. Attribute names (age, newName) do not use colons. The plus sign is valid for numeric addition.

3. Final Answer:

   Missing comma between updates. -> Option C

4. Quick Check:

   Separate multiple SET updates with commas [OK]

Hint: Separate multiple SET updates with commas [OK]

Common Mistakes:

• Omitting commas between attribute updates
• Incorrectly placing colons before attribute names
• Misplacing colons in attribute names

5. You want to update a DynamoDB item to set the attribute status to "active" only if it does not exist, and also increment loginCount by 1. Which UpdateExpression correctly does this?

hard

A. SET status = if_not_exists(status, :active), loginCount = loginCount + :inc

B. SET status = :active, loginCount = loginCount + 1 IF NOT EXISTS status

C. SET status = :active IF NOT EXISTS status, loginCount = loginCount + :inc

D. SET status = :active, loginCount = loginCount + :inc WHERE status = NULL

Solution

1. Step 1: Understand conditional setting with if_not_exists

   The function if_not_exists(attribute, value) sets the attribute only if it does not exist, which matches the requirement for 'status'.

2. Step 2: Check increment syntax and placeholders

   Incrementing 'loginCount' by ':inc' is correct. SET status = if_not_exists(status, :active), loginCount = loginCount + :inc uses placeholders properly and combines both updates in one SET expression.

3. Step 3: Evaluate other options

   Options B, C, and D use invalid syntax like 'IF NOT EXISTS' outside functions or WHERE clauses which are not valid in UpdateExpression.

4. Final Answer:

   SET status = if_not_exists(status, :active), loginCount = loginCount + :inc -> Option A

5. Quick Check:

   Use if_not_exists() to set only if missing [OK]

Hint: Use if_not_exists() to set attribute only if missing [OK]

Common Mistakes:

• Trying to use IF NOT EXISTS outside if_not_exists() function
• Using WHERE clause in UpdateExpression
• Not using placeholders for values