Date and timestamp types in MongoDB - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the MongoDB data type used to store dates and times?

MongoDB uses the Date type to store dates and times. It stores the number of milliseconds since the Unix epoch (January 1, 1970).

beginner

How do you create a new Date object in MongoDB shell?

You create a new Date object by calling new Date(). For example, new Date() returns the current date and time.

intermediate

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

Date stores a specific point in time with millisecond precision. Timestamp is mainly used internally for replication and stores a 64-bit value with a seconds part and an increment part.

beginner

How can you query documents with a date field greater than January 1, 2023?

Use a query like { dateField: { $gt: new Date('2023-01-01T00:00:00Z') } } to find documents where dateField is after January 1, 2023.

intermediate

Why is it important to store dates in UTC in MongoDB?

Storing dates in UTC avoids confusion caused by time zones and daylight saving changes. It ensures consistent date and time values across different systems and locations.

Which MongoDB type stores date and time with millisecond precision?

A String

B Timestamp

C Date

D Integer

The Date type stores date and time with millisecond precision in MongoDB.

How do you create a Date object for the current time in MongoDB shell?

A Date.now()

B new Date()

C Timestamp()

D new Timestamp()

new Date() creates a new Date object with the current date and time.

What is the main use of the Timestamp type in MongoDB?

A Storing time zones

B Storing user birthdates

C Storing string dates

D Internal replication and oplog entries

Timestamp is mainly used internally for replication and oplog entries in MongoDB.

Which query finds documents with a date after January 1, 2023?

A { dateField: { $gt: new Date('2023-01-01T00:00:00Z') } }

B { dateField: { $eq: '2023-01-01' } }

C { dateField: new Date('2023-01-01') }

D { dateField: { $lt: new Date('2023-01-01') } }

Use $gt with a Date object to find dates greater than January 1, 2023.

Why should dates be stored in UTC in MongoDB?

A To avoid time zone confusion

B To speed up queries

C To save storage space

D To support string formatting

Storing dates in UTC avoids confusion caused by time zones and daylight saving changes.

Explain the difference between MongoDB's Date and Timestamp types and when to use each.

Think about precision and internal MongoDB operations.

Describe how to query documents by date in MongoDB and why storing dates in UTC is important.

Consider query syntax and time zone handling.

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