[11.x] Added useCascadeTruncate
method for PostgresGrammar
#53343
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the current version of Laravel, the
cascade
option is used for thetruncate
in Postgres. However, this behavior is not expected by many developers (issue #35157) as Postgres by default uses therestrict
optionfor
truncate
(https://www.postgresql.org/docs/current/sql-truncate.html#id-1.9.3.181.6).For Laravel 11.x, it is proposed to add a new
useCascadeTruncate
method in thePostgresGrammar
, allowing developers to disable the cascade behavior. This provides more control over how thetruncate
operation behaves in Postgres.By default, the
cascade
behavior remains enabled in version 11.x to avoid BC.Future Plans:
For versions 12.x or 13.x, we may consider changing the default behavior to disable the
cascade
option fortruncate
.The upgrade notes will state that this behavior can be easily restored using the
PostgresGrammar::useCascadeTruncate()
method.