Realm
77 results found
-
Kotlin Multiplatform Support
It would be awesome to have a Kotlin multiplatform SDK.
5 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…
5 votes -
More examples
I think if there are more examples especially videos of how to setup and do small projects maybe on YouTube, Realm definitely reach more boarder audiences. Also it will help less experienced people.
4 votes -
.NET MAUI Support
.NET Maui is evolution of Xamarin.Forms. The former will replace later in second quarter of 2022, probably in April, 2022. The developer experience is going to be much better with Maui. Lots of the developers have already started experimenting with maui.
Lack of support from Realm is a blocker for those who have already started to migrate their apps from Xamarin.Forms to Maui and for those who want to develop there new apps with Maui.4 votes -
Add Android Studio plugin to replace Realm Studio
It's fairly unwieldy to use Realm Studio compared to SQLite support in Android Studio, which is in the App Inspection Tool window. I think it should be relatively easy to create a similar plugin for Realm. It would remove a large disadvantage compared to SQLite for Android developers and it would help rapid development.
3 votes -
Realm GraphQL returning “null” when using a GraphQL alias
The issue I am having is with GraphQL aliases. Currently I can run the following query with this result:
Query:
query {
event {
action
}
}
Result:{
"data": {
"event": {
"action": "create"
}
}
}
Although when I try to use an alias for one of the “action” field, it gives me a null value:
Query:query {
event {
something: action
}
}
Response:{
"data": {
"event": {
"something": null
}
}
}
Is GraphQL aliasing not available for the Realm GraphQL API, or am I doing something wrong on my end?3 votes -
Be able to Download Users listing in App Users
Would be nice if we could export out the user listing under Users (App Users), the login "Devices" details are also found there. It could provide us with more insights into how our users access to the application (Web or Mobile, browser version and etc..)
3 votes -
3 votes
-
Azure DevOps Repo integration with AtlasApp services.
Currently, App Services only has built in integration with Github, and no other online code repositories. Need support for Azure DevOps Repo integration with AtlasApp services code !.
3 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).
3 votes -
Integrate Gridfs in the realm sdk
Enable the use of gridfs with stitch apps in android.
3 votes -
MongoDB support for db.collection.distinct() in SDKs
Add distinct() function to the SDK. The ability of displaying unique values of a field will be useful.
3 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…
3 votes -
Ability to dynamically create/destroy realms
I would like to be able to dynamically create and destroy realms from my swift and java mobile apps. I imagine features in my mobile app that would be best served by a “temporary” realm
3 votes -
Native Codable Support for BSON Document
Supporting the codable protocol would clear out a lot of pain points in the swift sdk. I understand realm objects are classes not structs but implementing some kind of native conversion to Realm Objects would massively widen the set of use cases. Converting BSON docs from Remote access and GraphQL Queries to Realm objects is messy and lack any documentation. Having some kind of codable support would allow search functions and advanced MongoDB queries on a database with millions of objects without worrying about the sync infrastructure. It might not seem pertinent if you consider utility apps but if we…
2 votes -
Redesign documentation
Documentation is harder to follow then it should be.
Wanting to use realm over firebase but can't help but feel the time I waste navigating the docs would be worth just having used firebase...Absolutely love the feature sets I see but just not that clear how to implement them :/.
In particular I have seen conflicting messaging around authentication, some places advise that mongo app services authentication is not intended as a full authentication and should use other platforms. Why?That made me look at firebase auth with realm ... using custom jwt. Surely you can just create a…
2 votes -
Realm Golang SDK
For backend Realm DB generation and management, please provide a Golang SDK.
2 votes -
2 votes
-
Realm.open() method creating realm when not exists, should be made optional
Realm.open() method used in Middle Tier to fetch data would not find the realm and is waiting for data sync to happen from the device. This method can create a new realm if it does not exist which is not applicable in the context of the Middle Tier apps. Requesting an update to have this default realm creation functionality to be made optional based on a supplied optional parameter.
2 votes -
Provide utility function to allow easier reading and usage of ObjectIds
Provide a utility that allows easier parsing of ObjectIds when they're returned to the client. As it stands, ObjectIds are returned as UInt8Arrays and cannot be readily used in the BSON.ObjectId constructor. Being able to retrieve specific items by ObjectId is necessary and the only way to do this dynamically (without knowing the hex string beforehand) is to retrieve the items and then use the returned id; however, as it stands, using the returned id is obfuscated and impractical.
I am now having to use the following workaround:
const toHexString = (bytes) =>
bytes.reduce((str, byte) => str + byte.toString(16).padStart(2, "0"),…2 votes
- Don't see your idea?