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.