Talk:Truncate (SQL)

Computing Low‑importance

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles
Low	This article has been rated as Low-importance on the project's importance scale.

Databases (inactive)

This article is within the scope of WikiProject Databases, a project which is currently considered to be inactive.DatabasesWikipedia:WikiProject DatabasesTemplate:WikiProject DatabasesDatabases articles

DDL

Is it really a DDL operation? I thought the whole idea was that it affected data/content and didn't affect metadata/structure. It feels much more like DML to me. Mhkay (talk) 16:36, 17 November 2022 (UTC)[reply]

There's something better than "feels" --- it's explicitly documented in "Data manipulation" section in ISO SQL (sql:2011 and sql:2016). 5.178.229.209 (talk) 22:50, 16 May 2023 (UTC)[reply]

I strongly agree with Mhkay:

In SQL:2023 it's in the SQL data change statement category according to [1]https://standards.iso.org/iso-iec/9075/-2/ed-6/en/ISO_IEC_9075-2(E)_Foundation.bnf.txt, i.e. a DML statement.

I assert that the correct definition is product dependent:

If the DBMS implements it in a way where triggers are not fired by TRUNCATE, then it's a DDL, because it's essensially a short-hand for DROP+CREATE.
If the DBMS implements it as as a logical synonym with an unconstrained DELETE, then natural logic puts it in the DML category.

Troels Arvin (talk) 07:35, 13 November 2024 (UTC)[reply]