[12.x] Add check constraints support for database schema #56000
Closed
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.
Add Database Check Constraints Support
Overview
This PR adds native support for database check constraints to Laravel's Schema Builder, bringing a long-requested feature that enhances data integrity at the database level.
Check constraints allow you to enforce business rules directly in the database, ensuring data consistency regardless of how data is inserted or updated. This is particularly valuable for multi-application environments or when data integrity is critical.
Usage
Database Support
*SQLite limitations handled with clear exceptions
Features
where()
,orWhere()
,whereIn()
,whereNotIn()
Implementation Highlights
@RequiresDatabase
attributes to ensure compatibilityTesting Note
The current test suite covers the main functionality across all databases. If this feature direction is approved, I can add more comprehensive grammar-specific tests and additional edge case coverage as needed.