Ravindra BagaleCourses & study guides मराठी Track your progress

11. MySQL Part 2: UPDATE, ALTER, DELETE, Keys, Constraints and Users

11.4 DELETE, TRUNCATE and DROP

By Last updated:

Teen commands – teen vegle parinam. Interview madhe "DELETE vs TRUNCATE vs DROP" ha prashna jawal jawal nakki yeto.

DELETE FROM enrollments WHERE score < 50;       -- remove selected rows
DELETE FROM enrollments;                        -- remove all rows (structure stays)
TRUNCATE TABLE enrollments;                     -- remove all rows fast, reset AUTO_INCREMENT
DROP TABLE enrollments;                         -- remove the table itself
DROP TABLE IF EXISTS enrollments;               -- no error if missing
Point DELETE TRUNCATE DROP
Type DML DDL DDL
What goes Selected rows (or all) All rows Rows and table structure
WHERE allowed Yes No No
Rollback (InnoDB) Yes, inside a transaction No (implicit commit) No (implicit commit)
AUTO_INCREMENT Continues from last value Reset to 1 Table is gone
Triggers fire Yes (DELETE triggers) No No
Speed on large tables Slower (row by row, logged) Fast Fast
Table referenced by a foreign key Allowed if no child rows break Fails Fails (drop child first)

Why this matters for security

An application database user should almost never have DROP or TRUNCATE rights. If an attacker achieves SQL injection through a user that only has SELECT, INSERT, UPDATE, DELETE on one database, they cannot drop your tables. Least privilege limits the blast radius.

Ravindra Bagale's Tip

Many students only say "TRUNCATE is a faster version of DELETE". Go further: TRUNCATE is DDL, it can't be rolled back, AUTO_INCREMENT is reset, and triggers don't run. Mention these four points and the interviewer will be happy. And there's no undo after DROP – a backup is the only way back.

Practice task

Create a copy table with CREATE TABLE enroll_copy AS SELECT * FROM enrollments;. Try DELETE with ROLLBACK, then TRUNCATE, insert a row and note its id, then DROP the copy.

Extended teaching notes

Why this lesson matters

Use this lesson to strengthen systems you own: understand the risk, practise safely in a lab, then write and apply the fix.

Apply the fix across stacks

Same class of bug, same idea in every language.

Java / Spring Boot

Parameterise queries, encode output, CSRF tokens, limited Actuator, dependency scanning.

ASP.NET Core

EF Core / parameterised SQL, Razor encoding, HTTPS, Data Protection.

Node.js / Express

helmet, parameterised SQL, npm audit, avoid eval and shell concat.

Python / Django / Flask / FastAPI

ORM, autoescape, pip-audit, Bandit; never shell=True with user input.

PHP / Laravel

PDO/Eloquent, Blade escaping, composer audit.

Go / Ruby

database/sql placeholders / ActiveRecord; html/template / ERB escaping; govulncheck / Brakeman.

nginx / Apache / Tomcat

Hide versions, TLS, security headers, least-open ports.

MySQL / PostgreSQL / MongoDB / Redis

Private networks, auth on, least-privilege users, no 0.0.0.0/0.

AWS / Azure / GCP

Roles not long-lived keys, private data stores, cloud audit logs on.

Mini case study

Suppose we are on a purple-team exercise for an Indian mid-size company (sample data). Red notes a technique from this lesson against a lab clone. Blue must show the control that stops it, the log that would have fired, and the ticket that hardens production. That is the standard this course trains you for.

Defender's worksheet (do this today)

  1. Write the lesson title, date and the exact lab target you are allowed to use.
  2. List three owned systems (VMs, apps, or cloud accounts) where this lesson applies.
  3. Run one safe check from the lesson on a lab system only. Paste the command and output.
  4. Write a two-sentence fix you would give a teammate.
  5. Name one related public advisory (CERT-In, CISA, NVD, or a vendor bulletin) with its date.

Indian workplace (sample data)

Suppose we are a junior analyst at Infosys, TCS, Wipro or a fintech SOC in Bengaluru/Pune. Turn this lesson into one checklist item with an owner, a due date and a place to store evidence (ticket + screenshot).

Global practice

Compare your notes with OWASP, CIS Benchmarks, NIST CSF/IR guidance or a cloud Well-Architected security question. Write five lines on what overlaps.

Everyday analogy

Explain the risk and the fix to a family member without jargon. If they can repeat the warning, you understand it well enough to teach juniors.

Key terms

  • Control: a safeguard (patch, config, process, detection).
  • Finding: a weakness backed by evidence.
  • Remediation: the fix plus how you verified it.
  • Scope: systems you have written permission to touch.
  • Least privilege: only the access the task needs.
  • Defence in depth: several layers so one failure does not end the story.

Common mistakes

  • Skipping written permission "just for a quick scan".
  • Practising on hostel, office or public targets without authorisation.
  • Collecting tool output without writing the fix.
  • Copying attack steps onto production to "verify". Defenders verify with versions, configs and patches.
  • Publishing screenshots that contain secrets, cookies or internal hostnames.

Recap

  • Evidence, fix, owner, date.
  • Own lab only.
  • Fix > spectacle.