-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Upgrade to core 14.9.0 #8597
Upgrade to core 14.9.0 #8597
Conversation
a7ab28c
to
ce14c10
Compare
ce14c10
to
78c5b3d
Compare
CHANGELOG.md
Outdated
([Core #7670](https://github.com/realm/realm-core/issues/7670), since v14.6.0). | ||
* Inserting the same link to the same key in a dictionary more than once would incorrectly | ||
create multiple backlinks to the object. This did not appear to cause any crashes later, but would | ||
have affecting explicit backlink count queries (eg: `$0.links.count`) and possibly notifications. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We either don't support this query at all or it has a different syntax.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is referring to queries on backlinks for example $0.linkingObjects.count == 3
where
class TestObject: Object {
@Persisted var objectCol: TestObject?
@Persisted(originProperty: "objectCol")
var linkingObjects: LinkingObjects< TestObject >
}
And the return count will be wrong because it will create multiple backlinks instead of just one.
Correct me if I'm wrong @tgoyne
I don't think we can merge this separately from #8546 because this includes the protocol version bump which indicates that we're collections-in-mixed aware. |
78c5b3d
to
3c83c50
Compare
f36ed09
to
79e437e
Compare
79e437e
to
ecefddc
Compare
f2e21bf
to
b9a8602
Compare
b9a8602
to
3c0a9f8
Compare
Upgrade to core 14.9.0