Realm
-
Cascading Deletes
Please add support for cascading deletes.
Related GitHub Issues:
https://github.com/realm/realm-core/issues/746
https://github.com/realm/realm-java/issues/1104
https://github.com/realm/realm-cocoa/issues/118611 votes -
File/Binary Data type within Realm Database
Example:
A new type could be defined, such as RealmFile. A RealmObject could have a RealmFile field or even a RealmList<RealmFile> field. Just like all other RealmObjects, this would simply be a proxy and wouldn't contain the actual file/binary data. To access or update the data in the RealmFile you would get an InputStream or OutputStream. Realm handles the rest in terms of syncing, caching, linking, etc. I know that Realm itself isn't really designed for arbitrarily large files, so the data contained in a RealmFile wouldn't necessarily need to be put into Realm. But it would be managed and…
4 votes -
Revision History
It would be great if revision history could be kept, either on individual RealmObjects, groups of RealmObjects, or the Realm as a whole. There could be a way to specify the fidelity of the revisions (e.g. every change or every X minutes) and a way to specify a TTL (e.g. last 30 days). If the Realm is synced, the local Realm could purge its cache of revisions older than the TTL and there could be an API to retrieve these when needed. Additionally, there could a (separate) TTL for permanent deletion of revisions as to keep the Realm from growing…
2 votes -
Inheritance / Polymorphism
Support for polymorphism would be a huge plus. In particular, being able to define a class structure and then query for a base class (or interface?) to get a list of all the various concrete classes.
Related GitHub Issue: https://github.com/realm/realm-java/issues/761
2 votes -
Single unified GeoJSON type
Generating a schema and consuming GeoJSON data in Realm is painful. Since GeoJSON has multiple 'types', Realm forces us to store a serialized string version of our GeoJSON, or to abstract our data out so that all GeoJSON objects follow the same generalized schema, which breaks some of the conveniences of GeoJSON.
Realm should allow for a GeoJSON type OR allow the schema to be dynamic (such as supporting ORs in the schema language itself).
1 vote -
Add more documentation about schema changes
I made a substantial change to my schema that was not covered in the existing documentation. I resolved the problem based upon the information Ian Ward gave in this thread: https://developer.mongodb.com/community/forums/t/performing-destructive-changes-to-synced-realm/10757/11. This really should be in the documentation.
1 vote -
1 vote
-
disable rules filter
currently you can only remove filters, why not add a disable option so you can keep them for later? (e.g. testing)
1 vote -
Query Realm using MongoDB syntax
Now that Realm and MongoDB are so close, it would be nice to be able to use MongoDB-style queries on Realm as well. It seems to me that an object-based query language makes much more sense than a string-based one nowadays.
1 vote
- Don't see your idea?