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

Swift docs should make it clear that filtering by someListOfPrimitives.@count isn't supported #6079

Closed
sadlerjw opened this issue Feb 5, 2019 · 2 comments

Comments

@sadlerjw
Copy link

sadlerjw commented Feb 5, 2019

Goals

Filter a List of primitives by @count using RealmSwift, since the docs suggest this is possible:

The aggregate expressions @count, @min, @max, @sum and @avg are supported on List and Results properties, e.g. realm.objects(Company.self).filter("employees.@count > 5") to find all companies with more than five employees.

https://realm.io/docs/swift/latest/#queries

Expected Results

The docs should make it clear that filtering on @count on a List property is only supported for relationships, not primitives

Actual Results

Crash, as per several other issues: #5832, #5491, etc.
It turns out this isn't yet supported, as documented in #5334

Steps to Reproduce

Please see linked issues

Code Sample

Please see linked issues

Version of Realm and Tooling

ProductName:	Mac OS X
ProductVersion:	10.14.2
BuildVersion:	18C54

/Applications/Xcode.app/Contents/Developer
Xcode 10.1
Build version 10B61

/usr/local/bin/pod
1.5.3
Realm (3.7.5)
RealmSwift (3.7.5)

/bin/bash
GNU bash, version 3.2.57(1)-release (x86_64-apple-darwin18)

carthage not found
(not in use here)

/usr/local/bin/git
git version 2.20.1
@RealmBot
Copy link
Collaborator

RealmBot commented Jul 2, 2020

➤ Lee Maguire commented:

[~chris.bush] is this something you could take a look at?

@leemaguire
Copy link
Contributor

leemaguire commented Jul 2, 2020

I have flagged this with our docs team.

@RealmBot RealmBot closed this as completed Jul 2, 2020
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 17, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants