What's the benefit over core's timestamp field if you're saving an int(11) anyway?

Created on 14 May 2023, almost 2 years ago
Updated 15 June 2023, almost 2 years ago

Problem/Motivation

Wouldn't it be more efficient to either:

  1. use the core's timestamp field type and adding a widget/formatter that removes the date selection/display
    (timestamp formatter already includes the php date "Custom" format AND allows reusing predefined date formats AND converting to specific timezones)
  2. save less data to the database: 1 day = 24 hours = 86400 seconds = max value, that can be expressed with an int(5) instead of int(11)

??

💬 Support request
Status

Active

Version

2.0

Component

Documentation

Created by

🇮🇹Italy kopeboy Milan

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Production build 0.71.5 2024