Skip to content
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.

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

DOC filterAny() many-many aggregate conjunction #266

Merged
Merged
Changes from all commits
Commits
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/04_Changelogs/5.1.0.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,13 +13,16 @@ title: 5.1.0 (unreleased)
## Features and enhancements

### Other new features

- You can now exclude specific `DataObject` models from the check and repair step of `dev/build` - see [ORM Performance](/developer_guides/performance/orm/#skip-check-and-repair) for more information.
- You can change what `SearchFilter` the `TreeDropdownField` uses with yaml configuration - see [ORM Performance](/developer_guides/performance/orm/#treedropdownfield) for more information.
- The [`i18nTextCollector`](api:SilverStripe\i18n\TextCollection\i18nTextCollector) now collects strings for ORM properties (e.g. `$db` fields) in `DataObject` and `Extension` classes, and from themes. See [i18n - collecting text](/developer_guides/i18n/#collecting-text) for more details.
- Extensions which modify permissions for [`Group`](api:SilverStripe\Security\Group) records which return `true` will be respected, the same as when modifying permissions for any other `DataObject` record.

## Bug fixes

- [`DataList::filterAny()`](api:SilverStripe\ORM\DataList::filterAny()) queries on many-many relations that use an aggregate `HAVING` clause now correctly use an `OR` conjunction rather than an incorrect `AND` conjunction.

This release includes a number of bug fixes to improve a broad range of areas. Check the change logs for full details of these fixes split by module. Thank you to the community members that helped contribute these fixes as part of the release!

<!--- Changes below this line will be automatically regenerated -->
Expand Down