liveBook · Manning

Time

As explained in Grokking Relational Database Design

A TIME data type stores a time of day without calendar-date information.

A TIME data type stores a time of day without calendar-date information. Use it when an event’s position during the day matters, such as a review_time value. section 4.8

Choose TIME when:

  • You need to record only the time, not the date. section 4.8
  • You are tracking when something occurs during the day. section 4.8
  • You do not need a complete historical moment or automatic time-zone conversion. section 4.8

A review time

A value of '14:30:00' represents 2:30 p.m. Store a review_time attribute as TIME when the review’s time of day matters but its calendar date does not. section 4.8

How Grokking Relational Database Design covers it

How deep it goes
Defines TIME and distinguishes it from related temporal types without discussing implementation details.
Examples
Uses a review_time attribute and the value '14:30:00' to illustrate time-of-day storage.
What it assumes
Introduces temporal-type choices from the distinction between dates, times, combined values, and cross-time-zone moments.
How it connects
Connects TIME with DATE, DATETIME, TIMESTAMP, UTC, and time-zone handling.

Also explained in

Compare how 2 books explain time →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Grokking Relational Database Design. The section links point to the parts of the book it draws on.