Skip to main content
Gathering Interest

Improve FDM Querying

Related products:Data Modeling
Noah Karsky
Aditya Kotiyal
+5
  • Noah Karsky
    Noah Karsky
  • Diego Garzon
  • Bartosz Czernia
  • Aditya Kotiyal
    Aditya Kotiyal
  • Gayatri Babel
  • Sarah Behrens
  • Abram Ziegelaar
    Abram Ziegelaar
  • Asan Arifov
  • Mary Spanjers
  • Rajeev z ranjan

We have an aggregation resolver, but we are unable with this resolver to group the data using the "Foreign key" for another object type as the group key. I think it would be a cool resource to suggest  improvements to the tool in the future

 

@Lucas Leocardo Araujo 

4 replies

gedi
Seasoned Practitioner
  • Seasoned Practitioner
  • 31 replies
  • December 1, 2023

Thank you for sharing your insightful idea, Ibrahim!
We greatly appreciate your contribution. Stay tuned for updates on how we plan to proceed.


Dilini Fernando
Seasoned Practitioner
Forum|alt.badge.img+2
  • Seasoned Practitioner
  • 671 replies
  • December 8, 2023
The following idea has been merged into this idea:

All the votes have been transferred into this idea.

Forum|alt.badge.img

@ibrahim.alsyed - I’m a little uncertain as to what you mean by “group the data using the "Foreign key" for another object type”? Is this an SQL “group by” like functionality you’re asking for here?


Forum|alt.badge.img+2

@Thomas Sjølshagen , what Ibrahim meant is that imagine an object type called employee with the following structure:

type Employee {

name: String

age: Int

manager: Manager

}

If i want to make a query using the GraphQL API to group and count employees who have a specific manager, the graphQL API does not provide us with this functionality. We need to use the Rest API to perform this operation.

 

 


Reply


Cookie Policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie Settings