1 views collected around this technical thread.
A developer discovers a bug where a time component displays incorrect dates because the backend switched timestamp values from numbers to strings, and learns how to correctly parse timestamps in JavaScript using Dayjs and defensive Number conversion.
This article explains why storing dates as strings is inefficient, compares MySQL DATETIME and TIMESTAMP—including storage size, range, timezone handling, and performance—and discusses when to use numeric Unix timestamps or PostgreSQL equivalents for reliable time data management.
When storing dates in MySQL or PostgreSQL, avoid VARCHAR fields and select between DATETIME (no time‑zone, larger range) and TIMESTAMP (UTC conversion, smaller range) based on whether automatic time‑zone handling and the 2038 limit suit your application, with Unix timestamps as a high‑performance alternative.
This article explains why storing dates as strings is problematic, compares MySQL's DATETIME and TIMESTAMP types—including their storage size, range, and timezone behavior—provides practical SQL examples, discusses numeric Unix timestamps, and offers guidance on selecting the most suitable type for different scenarios.
Choosing the proper MySQL or PostgreSQL date/time column—avoiding string types, understanding DATETIME’s literal storage versus TIMESTAMP’s automatic UTC conversion, considering PostgreSQL’s TIMESTAMP WITH/WITHOUT TIME ZONE equivalents, and weighing numeric Unix timestamps for speed—ensures correct time‑zone handling, storage efficiency, and future‑proof range.
This guide details a secure third‑party API design, covering API key generation, request signing with timestamps and nonces, permission division, CRUD endpoint definitions, unified response structures, and best‑practice security measures such as HTTPS, IP whitelisting, rate limiting, logging, and idempotency handling.
This article explains GMT, UTC, time zones, local time, and daylight‑saving time, outlines their effects on game server and client logic, presents three common handling strategies, lists typical bugs, and provides a detailed testing checklist for reliable time‑related features.
Hotlinking attacks steal popular media by fetching resources from major platforms, but developers can protect assets using anti-leech methods such as Nginx referer checks, SpringBoot filters, token validation, timestamp verification, and graphical captchas, each with strengths and limitations against forged requests.
This article presents a comprehensive design scheme for third‑party API interfaces, covering access‑key/secret‑key generation, permission segmentation, signature flow and rules, anti‑replay mechanisms, token handling, and concrete Java code examples for secure request validation.
This article explains the PHP filectime() function, how it returns a file's creation timestamp, and provides a complete example showing file existence checking, timestamp conversion with date(), and output handling, while also mentioning related functions such as filemtime() and fileatime() for broader file time management.
This article analyzes how MySQL binlog records timestamps and exec_time for GTID, BEGIN, Table_map, Write, and Xid events on both master and slave, explains the calculation of original_commit_timestamp and immediate_commit_timestamp, and provides formulas and source‑code references to help diagnose replication delay.
The article presents a comprehensive guide to designing secure third‑party APIs, covering access‑key/secret‑key generation, token management, signature algorithms, timestamp and nonce anti‑replay mechanisms, permission granularity, request logging, rate limiting, and example Java and SQL implementations.
This article explains the meaning, generation process, and operational impact of the new immediate_commit_timestamp and original_commit_timestamp fields in MySQL 8.0 binlog events, including how they affect replication delay calculations, warning handling, and precise monitoring of transaction commit times.
This article explains how to protect microservice APIs from tampering and replay attacks by using HTTPS, request signing, nonce‑timestamp mechanisms, and AppId/AppSecret authentication, and demonstrates a complete Java/Spring implementation with a responsibility‑chain based verification filter.
This article explains how to use PHP's timestamp functions—including time(), strtotime(), date(), and mktime()—to obtain current timestamps, convert strings to timestamps, format dates, handle time zones, and perform relative time calculations with practical code examples.
This article explains the PHP date() function, covering its syntax, required and optional parameters, common format characters for year, month, day, hour, minute and second, additional textual options, usage for timestamp conversion, and timezone considerations, helping developers handle date and time tasks efficiently.
This article recounts how Ken Thompson and Dennis Ritchie devised the Unix Epoch Time as a simple integer timestamp, explains its advantages, the 32‑bit limitation leading to the Y2K38 issue, and describes the transition to 64‑bit timestamps in modern systems.
This article explains why Redis experiences key‑setting race conditions under high concurrency and presents two practical solutions—using a distributed lock with timestamps and serializing writes via a message queue—to ensure correct ordering and data consistency.
This article outlines essential API security mechanisms—including encryption, signing, timestamp validation, AppId authentication, rate limiting, blacklist handling, and data validation—and provides practical Java implementation examples for each technique.
This article evaluates how MySQL stores time using datetime, timestamp, and bigint fields by inserting 500,000 records and measuring query, grouping, and sorting speeds, concluding that bigint generally offers the best performance for time‑range operations while timestamp saves space when no manipulation is needed.