Skip to content

Realm

← MongoDB Feedback Engine

How can we improve Realm (SDKs and Local DB)?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • or

3 results found

  1. 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?

    6 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Realm (General)  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  2. Would be great to have distinct as GraphQL operator

    Currently GraphQL operator does not have distinct
    https://www.mongodb.com/docs/atlas/app-services/graphql/types-and-resolvers/#input-types
    Would be good to have this for improved performance. Currently we return all documents, and UI will perform the distinct operation which can be a problem if there are many documents in the collection.

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Realm (General)  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  3. 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…

    3 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Realm Swift SDK  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
  • Don't see your idea?

Realm

Categories

Feedback and Knowledge Base

(thinking…)