Type conversion expressions ($toInt, $toString) in MongoDB - Step-by-Step Execution

Concept Flow - Type conversion expressions ($toInt, $toString)

Start with input value

↓

Apply $toInt or $toString

↓

Check if conversion is possible

↓

Return converted

↓

Output

The flow shows how MongoDB converts a value to integer or string using $toInt or $toString, checking if conversion is possible and returning the converted value or error.

Execution Sample

MongoDB

[
  { $project: { numberAsInt: { $toInt: "$numberStr" }, numberAsStr: { $toString: "$number" } } }
]

This aggregation stage converts a string field 'numberStr' to integer and an integer field 'number' to string.

Execution Table

Step	Input Value	Expression	Conversion Result	Notes
1	"123"	$toInt	123	String '123' converts to integer 123
2	123	$toString	"123"	Integer 123 converts to string '123'
3	"abc"	$toInt	Error or null	String 'abc' cannot convert to integer
4	true	$toString	"true"	Boolean true converts to string 'true'
5	null	$toInt	null	Null converts to null for $toInt
6	45.67	$toInt	45	Float 45.67 converts to integer 45 by truncation
7	"45.67"	$toInt	Error or null	String '45.67' cannot convert directly to int
8	Exit	-	-	No more conversions

💡 Execution stops after all input values are processed or conversion fails.

Variable Tracker

Variable	Start	After 1	After 2	After 3	After 4	After 5	After 6	After 7	Final
inputValue	"123"	123	"abc"	true	null	45.67	"45.67"	Exit	Exit
convertedValue	N/A	123	"123"	Error/null	"true"	null	45	Error/null	End

Key Moments - 3 Insights

Why does converting the string '45.67' with $toInt fail while the float 45.67 converts successfully?

Because $toInt can convert numeric types like float by truncation, but cannot convert strings with decimal points directly, causing an error or null (see execution_table row 6 and 7).

What happens when $toInt tries to convert a non-numeric string like 'abc'?

It results in an error or null because the string does not represent a valid number (see execution_table row 3).

How does $toString handle boolean values?

$toString converts boolean true or false to their string equivalents 'true' or 'false' (see execution_table row 4).

Visual Quiz - 3 Questions

Look at the execution_table, what is the conversion result of input value "123" with $toInt?

A 123

B "123"

C Error or null

D null

💡 Hint

Check execution_table row 1 under Conversion Result.

At which step does $toInt conversion fail due to invalid string input?

A Step 2

B Step 3

C Step 6

D Step 4

💡 Hint

Look for 'Error or null' in Conversion Result column in execution_table.

If the input value is boolean true, what does $toString convert it to?

A "true"

B true

C 1

D Error

💡 Hint

See execution_table row 4 Conversion Result.

Concept Snapshot

$toInt and $toString convert values to integer or string.
Use $toInt to convert strings or numbers to integers (floats truncate).
Use $toString to convert any value to string.
Invalid conversions return error or null.
Useful in aggregation pipelines for type consistency.

Full Transcript

This visual execution trace shows how MongoDB's $toInt and $toString expressions convert values. Starting with an input value, the expression attempts conversion. If successful, the converted value is returned; otherwise, an error or null is returned. Examples include converting string '123' to integer 123, integer 123 to string '123', and handling invalid conversions like string 'abc' to integer which fails. The trace highlights how floats convert by truncation and booleans convert to their string forms. This helps beginners understand step-by-step how type conversions behave in MongoDB aggregation pipelines.

Practice

1. What does the $toInt expression do in MongoDB aggregation?

easy

A. Converts a value to a date

B. Converts a value to an integer (whole number)

C. Converts a value to a boolean (true/false)

D. Converts a value to a string (text)

Solution

1. Step 1: Understand the purpose of $toInt

   The $toInt operator converts values to integers, which are whole numbers without decimals.

2. Step 2: Compare with other conversion types

   $toString converts to text, $toBool to boolean, and $toDate to date. So $toInt specifically converts to integer.

3. Final Answer:

   Converts a value to an integer (whole number) -> Option B

4. Quick Check:

   $toInt = integer conversion [OK]

Hint: Remember: Int means whole number, String means text [OK]

Common Mistakes:

• Confusing $toInt with $toString
• Thinking $toInt converts to decimal numbers
• Mixing up $toInt with boolean conversion

2. Which of the following is the correct syntax to convert a field age to string in a MongoDB aggregation pipeline?

easy

A. { $toInt: "$age" }

B. { $toString: age }

C. { $toString: "$age" }

D. { toString: "$age" }

Solution

1. Step 1: Identify correct operator and field reference

   The operator for string conversion is $toString. Field names must be referenced as strings with a $ prefix inside quotes, like "$age".

2. Step 2: Check syntax correctness

   { $toString: "$age" } uses correct operator and field reference. { $toString: age } misses quotes around field. { $toInt: "$age" } uses wrong operator $toInt. { toString: "$age" } misses $ sign before operator.

3. Final Answer:

   { $toString: "$age" } -> Option C

4. Quick Check:

   Use $ and quotes for fields, $toString for string conversion [OK]

Hint: Use $ before field names and operators in MongoDB [OK]

Common Mistakes:

• Omitting quotes around field names
• Forgetting $ before operator
• Using wrong operator for conversion

3. Given the document { "score": "85" }, what will be the result of this aggregation expression: { $toInt: "$score" }?

medium

A. 85 (as an integer)

B. "85" (as a string)

C. null

D. Error: Cannot convert string to int

Solution

1. Step 1: Understand input and conversion

   The field "score" is a string "85". Using $toInt converts this string to the integer 85.

2. Step 2: Confirm output type

   The output will be the number 85, not a string or error, because "85" is a valid numeric string.

3. Final Answer:

   85 (as an integer) -> Option A

4. Quick Check:

   String "85" to int = 85 [OK]

Hint: Numeric strings convert cleanly to integers [OK]

Common Mistakes:

• Expecting output to remain a string
• Thinking conversion causes error
• Confusing null with error

4. You wrote this aggregation expression: { $toInt: 123abc }. What is the problem?

medium

A. It returns null silently

B. It converts to integer 123

C. It converts to string "123abc"

D. Syntax error because 123abc is not a valid number or string

Solution

1. Step 1: Analyze the input value

   The value 123abc is not a valid number or quoted string. MongoDB expects a number or string literal for conversion.

2. Step 2: Understand MongoDB parsing rules

   Without quotes, 123abc is invalid syntax, causing a syntax error.

3. Final Answer:

   Syntax error because 123abc is not a valid number or string -> Option D

4. Quick Check:

   Invalid literals cause syntax errors [OK]

Hint: Always quote strings; invalid literals cause errors [OK]

Common Mistakes:

• Assuming partial conversion works
• Forgetting to quote strings
• Expecting silent null return

5. You have a collection with documents like { "value": 123 } and { "value": "456" }. You want to create a new field valueStr that is always a string. Which aggregation expression correctly converts value to string regardless of original type?

hard

A. { $toString: "$value" }

B. { $toInt: "$value" }

C. { $toString: value }

D. { $toString: { $toInt: "$value" } }

Solution

1. Step 1: Understand the data types

   Some values are numbers (123), some are strings ("456"). We want to convert all to strings.

2. Step 2: Choose correct conversion

   $toString converts any type to string. Using { $toString: "$value" } converts both numbers and strings to string type.

3. Step 3: Evaluate other options

   { $toInt: "$value" } converts to int, not string. { $toString: value } misses quotes around field name. { $toString: { $toInt: "$value" } } converts to int then string, unnecessary and may cause errors if string is non-numeric.

4. Final Answer:

   { $toString: "$value" } -> Option A

5. Quick Check:

   Use $toString with quoted field for consistent string conversion [OK]

Hint: Use $toString with "$field" to convert any type to string [OK]

Common Mistakes:

• Missing quotes around field name
• Using $toInt instead of $toString
• Unnecessary double conversion causing errors