Date and timestamp types in MongoDB - Step-by-Step Execution

Concept Flow - Date and timestamp types

Insert Date or Timestamp

↓

Stored as BSON Date or Timestamp

↓

Query or Update

↓

Returned as ISODate or Timestamp Object

↓

Use in Application or Aggregation

Dates and timestamps are stored in MongoDB as special BSON types and can be inserted, queried, and returned as ISODate or Timestamp objects.

Execution Sample

MongoDB

db.events.insertOne({name: "Meeting", date: new Date("2024-06-01T10:00:00Z")})
db.events.find({date: {$gte: new Date("2024-06-01T00:00:00Z")}})

Insert a document with a Date field and query documents with date greater or equal to a specific date.

Execution Table

Step	Action	Input/Condition	Result/Output
1	Insert document	{name: "Meeting", date: new Date("2024-06-01T10:00:00Z")}	Document stored with BSON Date type for 'date'
2	Query documents	Find documents where date >= new Date("2024-06-01T00:00:00Z")	Returns documents with date on or after June 1, 2024
3	Return result	Document with date field	Date shown as ISODate("2024-06-01T10:00:00Z") in output
4	Use timestamp	Insert with Timestamp(1710000000, 1)	Stored as BSON Timestamp type
5	Query timestamp	Find documents with timestamp >= Timestamp(1710000000, 0)	Returns matching documents with Timestamp fields
6	Exit	No more documents match query	Query ends

💡 Query ends when no more documents match the date or timestamp condition

Variable Tracker

Variable	Start	After Insert	After Query	Final
date	undefined	ISODate("2024-06-01T10:00:00Z")	ISODate("2024-06-01T10:00:00Z")	ISODate("2024-06-01T10:00:00Z")
timestamp	undefined	Timestamp(1710000000, 1)	Timestamp(1710000000, 1)	Timestamp(1710000000, 1)

Key Moments - 3 Insights

Why does MongoDB show dates as ISODate instead of a plain string?

MongoDB stores dates as BSON Date type internally, and the shell displays them as ISODate for clarity, as shown in execution_table step 3.

What is the difference between Date and Timestamp types in MongoDB?

Date stores a specific point in time, while Timestamp includes a time and an increment for ordering operations, as seen in execution_table steps 4 and 5.

Can I compare dates and timestamps directly in queries?

No, you must compare dates with dates and timestamps with timestamps separately, as shown in the query conditions in execution_table steps 2 and 5.

Visual Quiz - 3 Questions

Look at the execution_table, what type is the 'date' field stored as after insertion?

A BSON Date

B String

C Timestamp

D Number

💡 Hint

Check step 1 in execution_table where the document is stored with BSON Date type.

At which step does the query return documents with date on or after June 1, 2024?

A Step 1

B Step 2

C Step 4

D Step 6

💡 Hint

Look at the query action in step 2 filtering by date condition.

If you insert a document with a Timestamp type, which step shows this action?

A Step 3

B Step 5

C Step 4

D Step 6

💡 Hint

Step 4 shows insertion with Timestamp type.

Concept Snapshot

MongoDB stores dates as BSON Date type and timestamps as BSON Timestamp type.
Use new Date() to create dates and Timestamp() for timestamps.
Dates show as ISODate() in shell output.
Query dates and timestamps with $gte, $lt, etc., but compare types correctly.
Timestamps include an increment for operation ordering.
Dates represent specific points in time.

Full Transcript

In MongoDB, dates and timestamps are special data types stored in BSON format. When you insert a document with a date field using new Date(), MongoDB stores it as a BSON Date. Queries can filter documents by comparing these dates. The shell displays dates as ISODate for readability. Timestamps are different; they include a time and an increment and are used for operation ordering. You insert timestamps with the Timestamp() constructor and query them similarly but must keep date and timestamp types separate in queries. This visual trace showed inserting and querying both types step-by-step, tracking how values change and how MongoDB handles these types internally.

Practice

1. Which MongoDB data type is best for storing a human-readable date and time?

easy

A. Number

B. ISODate

C. String

D. Timestamp

Solution

1. Step 1: Understand MongoDB date types

   ISODate stores dates in a readable and standard format, suitable for queries and sorting.

2. Step 2: Compare with other types

   Timestamp is mainly for internal use, String and Number do not store dates natively.

3. Final Answer:

   ISODate -> Option B

4. Quick Check:

   Date type for readable time = ISODate [OK]

Hint: Use ISODate for readable and queryable dates [OK]

Common Mistakes:

• Confusing Timestamp with ISODate
• Using String to store dates
• Using Number for date storage

2. Which of the following is the correct way to create a date object for January 1, 2023 in MongoDB shell?

easy

A. Timestamp("2023-01-01")

B. new Date(2023-01-01)

C. ISODate("2023-01-01")

D. Date("2023-01-01")

Solution

1. Step 1: Recall MongoDB date creation syntax

   ISODate() is the correct function to create a date object in MongoDB shell.

2. Step 2: Check other options

   new Date() is JavaScript syntax but not recommended in MongoDB shell; Timestamp() is for internal timestamps; Date() returns string, not date object.

3. Final Answer:

   ISODate("2023-01-01") -> Option C

4. Quick Check:

   MongoDB date object = ISODate() [OK]

Hint: Use ISODate() to create dates in MongoDB shell [OK]

Common Mistakes:

• Using new Date() instead of ISODate()
• Using Timestamp() for normal dates
• Calling Date() without new keyword

3. Given the following MongoDB document:

{ "event": "meeting", "time": ISODate("2024-06-15T10:00:00Z") }

What will be the result of this query?

db.events.find({ time: { $gt: ISODate("2024-06-01T00:00:00Z") } })

medium

A. Returns documents with time after June 1, 2024

B. Returns documents with time before June 1, 2024

C. Returns all documents regardless of time

D. Syntax error in query

Solution

1. Step 1: Understand the query filter

   The query uses $gt (greater than) to find documents where time is after June 1, 2024.

2. Step 2: Check document time value

   The document time is June 15, 2024, which is after June 1, 2024, so it matches the filter.

3. Final Answer:

   Returns documents with time after June 1, 2024 -> Option A

4. Quick Check:

   $gt filter returns later dates [OK]

Hint: Use $gt to find dates after a given date [OK]

Common Mistakes:

• Confusing $gt with $lt
• Expecting syntax error
• Thinking it returns all documents

4. What is wrong with this MongoDB query to find documents with a timestamp field after a certain date?

db.logs.find({ timestamp: { $gt: "2024-01-01T00:00:00Z" } })

medium

A. The $gt operator is invalid

B. The query syntax is correct

C. The field name 'timestamp' is reserved

D. The date string should be wrapped in ISODate()

Solution

1. Step 1: Check the query filter value type

   The query compares the timestamp field to a string, but MongoDB expects a Date object for date comparisons.

2. Step 2: Correct the date format

   Wrapping the date string in ISODate() converts it to a Date object, making the query valid.

3. Final Answer:

   The date string should be wrapped in ISODate() -> Option D

4. Quick Check:

   Date comparisons need ISODate() objects [OK]

Hint: Wrap date strings with ISODate() for date queries [OK]

Common Mistakes:

• Using plain strings for date comparison
• Assuming $gt is invalid
• Thinking field names are reserved

5. You want to store user login times and also track the exact order of logins including multiple logins in the same second. Which MongoDB data type combination should you use?

hard

A. Use ISODate for login time and Timestamp for order tracking

B. Use only ISODate for both time and order

C. Use Timestamp for login time and String for order

D. Use String for both login time and order

Solution

1. Step 1: Understand the use of ISODate and Timestamp

   ISODate stores readable date/time; Timestamp is precise and used internally to track order of operations.

2. Step 2: Apply to login tracking

   Use ISODate to record when login happened, and Timestamp to track exact order if multiple logins occur at the same second.

3. Final Answer:

   Use ISODate for login time and Timestamp for order tracking -> Option A

4. Quick Check:

   ISODate for time + Timestamp for order = correct [OK]

Hint: Combine ISODate and Timestamp for time and order tracking [OK]

Common Mistakes:

• Using only ISODate loses order precision
• Using Timestamp for readable time
• Using strings instead of date types