SQL data manipulation language

Data modification statements

PostgreSQL

1. The CONTINUE IDENTITY and RESTART IDENTITY  options are supported, when unspecified  the CONTINUE IDENTITY option is implicit.
   
2. Truncating of rows is available in more than one table when listing them via commas in a single operator.
   
3. Cascade truncating can be done for tables having FOREIGN KEY constraints that reference the table:

TRUNCATE TABLE Truncate_test RESTART IDENTITY CASCADE;

Just a truncation takes place, but not only the deletion of related rows. I.e. if you add, among others, a row with NULL value in foreign key column to the child (referencing) table

INSERT INTO Trun_Ref VALUES(1), (2), (NULL);

Oracle

1. Oracle has not autoincrement function which could be specified in a column definition. Nevertheless autoincrement behaviour can be imitated with aid of sequence. For example, theTruncate_test table mentioned above could be created in Oracle in such manner:
   

   CREATE SEQUENCE u_seq
    START WITH     5
    INCREMENT BY   5;
   /
   CREATE TABLE Truncate_test (id INT PRIMARY KEY, val int);
   /
   INSERT INTO Truncate_test(id, val) 
   VALUES (u_seq.NEXTVAL,1);
   INSERT INTO Truncate_test(id, val) 
   VALUES (u_seq.NEXTVAL,2);
   INSERT INTO Truncate_test(id, val) 
   VALUES (u_seq.NEXTVAL,3);
   
   
2. Upon executing TRUNCATE TABLE Truncate_test command, the counter (sequence) is not being reset, and the numbering will be continued.
3. Cascade operations are not allowed, so TRUNCATE TABLE statement is not available when the table is referenced by a foreign key.

MySQL

1. The CONTINUE IDENTITY and RESTART IDENTITY options are not supported; a counter (AUTO_INCREMENT) is being reset to zero.
2. Cascade operations are similar to using DELETE statement, i.e. if foreign key has ON DELETE CASCADE option, related rows will be deleted only. This means that rows with NULL values in the foreign key column are being retained after truncating:
   

   TRUNCATE TABLE Truncate_test;