@taylorotwell Can you explain why this was reverted? You realize that this code causes EVERY table to be truncated that has a related constraint to the one referenced in DB::truncate() right? So, if you follow a typical design pattern where all of your tables are constrained with foreign keys, DB::truncate('anything') results in large-scale data destruction. That's super dangerous and isn't expected behavior when someone is doing DB::truncate('just-one-table').

https://www.postgresql.org/docs/9.1/sql-truncate.html

CASCADE

Automatically truncate all tables that have foreign-key references to any of the named tables, or to any tables added to the group due to CASCADE.

As a note, this behavior OVERRIDES any ON DELETE that you may have set in the database.

@taylorotwell could you please explain the reasoning behind this reversion?