Realm
47 results found
-
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 -
GridFS in Browser SDK
I could really use file upload/download in my application. I'm attempting to build a PWA in Angular and although we could write a whole other, server-side, api-based application to support file upload/download, it would really benefit the team if this was available in the Browser SDK
2 votes -
Realm C++ SDK cross-compile Qt(IOS)
It's always good idea to make it cross compile as core module can do.
1 vote -
Device Sync Access
Device sync is convenient but uncontrollable. For example, there are problems with database cache inconsistency, and occasionally synchronization errors may cause data rollback. These details cannot be controlled by programmers.
1 vote -
App service (app_id) security enhancement
App service (app_id) security enhancement.
I am developing an App and using Realm to store data on the device and to synchronize that with my Mongo DB. Realm features finally seems to be working fine, however
I was surprised that only the App id is needed to reach my App service programmatically from code. There is no APP secret or key pairs... It seemed even more vulnerable when experienced that the default password change urls and confirmation mail URLs has my APP id in them.So I dont see any gate which would prevent any of my apps users to…
1 vote -
Termination protection for realm apps
it is very easy to delete a realm app, once deleted we cannot restore the app or recreate with same appId in this case we will be forced to publish new versions of apps with new app IDs. also there are no access roles when it comes to app services which is a big security hazard for apps in production as any member can delete an app by mistake.
My Ideas are:
1. Introduce role based access for app services
2. give a restore app option for deleted apps (30 days before permanently getting deleted)1 vote -
Realm emulator
It would be helpful to be able to launch a local Realm emulator for development purposes with Realm SDK, and for testing the permissions rules. To avoid relying on a real instance.
Something similar to what Firebase supports:
- https://firebase.google.com/docs/emulator-suite
- https://firebase.google.com/docs/firestore/security/test-rules-emulator1 vote -
Support network proxy for Realm SDKs
I copy here the feedback received on a support case about the lack of network proxy support in the Realm SDKs. That feature might be of interest for other customers as well, particularly during a product development phase, when we are mainly working behind a corporate proxy.
"We deeply regret the inconvenience caused by the absence of proxy support in our SKDs at this time.
But, We have received an update from our production manager regarding the ==tentative plans== to address the APIs related to proxy settings for all of Realm software development kits (SDKs) in the upcoming quarters, specifically…
1 vote -
Support for North Europe(Azure) for App Services
Our clusters are in North Europe, Ireland, and we plan to migrate our App Services (now located in West Europe, Ireland, AWS) to be located in West Europe, Netherlands, Azure.
Support for North Europe, Ireland, Azure, region for App Services would be much appreciated. That way our Data Services and App Services would be fully aligned and with a better performance.
1 vote -
Use Enums in Generated Realm Object Models
When the JSON Schema for a collection contains a string enumeration, like the following:
{ "properties": { "_id": { "bsonType": "objectId" }, "enumExample": { "bsonType": "string", "enum": [ "Foo", "Bar", "Baz" ], "title": "The type of entity that was favorited, such as a Workout." } }, "required": [ "_id", "enumExample" ], "title": "EnumExample" }... the generated Realm Object Models don't take advantage of the limited possible values. I've generated all of the available languages, and they all generate variations of a simple
string.Here's TypeScript as an example:
…import Realm from "realm"; export type EnumExample = { _id:1 vote -
Realm Query Language Documentation: Sort, Distinct, Limit
Realm Query Language Documentation located here https://www.mongodb.com/docs/realm/realm-query-language/#sort--distinct---limit needs updating with more specific examples of how to implement SORT, DISTINCT and LIMIT. The documentation also appears to be out of date (?)
1 vote -
Automatic Syncing of Referenced Objects
Please implement the feature to automatically sync referenced objects when you add a subscription to the parent object. This would mitigate the need for multilayer subscriptions at every step.
1 vote -
Documentation for the path parameter of Configuration
The
pathparameter on the Configuration seems to be an important parameter when it comes to sync. This value should not be set when using sync. See the link to a forum post for more information.Overall, the configuration parameters could use some documentation.
1 vote -
Increased Authentication Visibility and Better Customization
Having a fully managed authentication through Realm has been great, it continues to save a lot of time developing authentication and security protocols. With that said, as my application's admin I feel like my visibility into authentication is sparse. I can not help my users when they run into issues and am concerned as our application continues to grow. My request is for more visibility into authentication, including, but not limited to the following...
- Last Login Date: Ability to run queries on this field in order to generate daily, weekly, and monthly user metrics, most importantly the number of logins…
1 vote -
encryption
A better encryption key rotation without write copy
1 vote -
Return count of inserted/updated records for BulkWrite and collection.insertMany( with duplicates)
On success, BulkWrite returns a null response as mentioned in the documentation - https://www.mongodb.com/docs/atlas/app-services/functions/mongodb/api/#collection.bulkwrite--. Can you please send correct response details ( no. of records inserted, no. of records updated ) ? The functionality works correctly but we need correct details returned for debugging issues instead of making a redundant find call to check the results.
When inserting with duplicates, mongo inserts unique records successfully and discards duplicates. However, in the response sent, it does not specify the number of successfully inserted records and the count of duplicates, whereas, this information is returned in normal mongo SDK insert
1 vote -
transfer authenticated user to another project
im surprised that nobody asked about this. firebase already have this functionality whereby i could export existing firebase firestore and authenticated users to another project.
in mongodb realm, collection and functionality can be export and imported. but existing authenticated users are not able to move. or maybe im missing something. i find this a big bummer when duplicating project for staging or testing or even for another client. i dont wish to need to do custom authentication todo this, but i am on the way todo it.
1 vote -
Track every Realm App's secret change in Deployment History
Currently, only deployed changes in Realm App are tracked in Deployment History and can be re-deployed but not secret changes. In the situation, if we deploy the change in Realm App new record is created in Deployment History with existing Secret with the current value 'v1', after that let's say we updated the same Realm's secret twice (with values 'v2' and after some time with 'v3'), such changes are not tracked, no new records in Deployment History. If we re-deploy last created record in Deployment History, it will also overwrite Secret's value from 'v3' to the old one 'v1'. Tracking…
1 vote -
Deep Copying Objects Across Realms (aka: Partitions)
Please have the SDKs allow to copy objects from one partition to another. Currently you have to manually do it, which isn't great but not horrible, until your object has nested Objects, List<>s or EmbeddedObjects (via referenced 'foreign_key' / _id) - that is when it gets nasty and cumbersome. In Legacy Realm when ever you copied a top-level object its nested Objects & List<>s were copied automatically. That is not the case anymore, in MongoDB's Realm each one has to be done manually.
Built-in deep copying Objects is further important since:
1) Using partition-based Realm leads to denormalizing your data,…1 vote
- Don't see your idea?