Skip to content

5.next: Add ExistsInNullable #8115

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 20, 2025
Merged

5.next: Add ExistsInNullable #8115

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions en/appendices/5-3-migration-guide.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -177,6 +177,9 @@ Validation
- ``ipOrRange()`` validation has has been added to check for an IP or a range (subnet).
- When validating within CakePHP marshalling context, the entity will be passed into the ``context`` argument for use inside custom validation rules.
This can be useful when patching partially and then needing to get that data from the entity instead of the passed data.
- ``existsInNullable()`` rule has been added. This rule allows ``null`` values in nullable composite foreign keys,
which is semantically correct for optional relationships. Use ``$rules->existsInNullable(['author_id', 'site_id'], 'SiteAuthors')``
instead of ``existsIn()`` when you want to permit null values in foreign keys.

View
----
Expand Down
Loading