0 views collected around this technical thread.
This article explains MySQL's storage architecture, compares the DELETE, TRUNCATE, and DROP commands, shows their performance and side‑effects, and provides practical guidance on choosing the safest and most efficient way to remove data from a MySQL table.
The article explains how many backend services use logical deletion—simply flagging or masking user data instead of physically removing it—to appear compliant with standards like China's GB/T 35273, while highlighting risks such as continued e‑bike control, fraud detection challenges, and missed logout handling.
This article explains the three primary ways to delete data in MySQL—using DELETE, TRUNCATE, and DROP—detailing their execution speed, underlying mechanisms, storage‑engine differences, and best‑practice considerations such as space reclamation and auto‑increment handling.
This article outlines ByteDance's comprehensive big‑data security framework, detailing current challenges, fine‑grained permission control, asset protection, data deletion capabilities, and the governance principles that balance compliance with operational efficiency.
The article explains the three primary MySQL data removal commands—DELETE, TRUNCATE, and DROP—detailing their execution speed, underlying mechanisms, impact on disk space for InnoDB and MyISAM engines, and best‑practice usage such as running OPTIMIZE TABLE after DELETE.
The article explains various ways programmers and DBAs can permanently delete server files, databases, tables, or data using Linux rm commands and SQL statements like DROP, TRUNCATE, and DELETE, illustrates the risks of accidental or malicious deletions, and offers practical tips for prevention such as careful command review, strict permission control, and regular backups.
This article explains the three primary ways to remove data in MySQL—DELETE, TRUNCATE, and DROP—comparing their execution speed, underlying mechanisms, impact on disk space, transaction behavior, and how to reclaim space with OPTIMIZE, while providing practical SQL examples and usage warnings.
A Shanghai court sentenced programmer He Mou to six years in prison for deliberately deleting all SaaS data of Weimeng, causing an eight‑day outage, over 300 million yuan in losses, and prompting a discussion on on‑premise versus cloud data protection strategies.
Through a step‑by‑step case study of a high‑traffic OLTP system, this article explains how evolving deletion logic—from simple full‑table scans to indexed intermediate tables and parallel processing—reduced daily expired‑data cleanup from several hours to under an hour, while addressing ORA‑01555 and clustering‑factor issues.