这是indexloc提供的服务,不要输入任何密码
Skip to content

RFC Aggregations and Grouping - GroupBy Support #9712

@dameleney

Description

@dameleney

Hasura GraphQL GroupBy

Motivation

Several requests have been filed to support GROUP BY within Hasura's auto-generated GraphQL schema.
#3478
#6953
#8127

"Group By" is a common function in SQL databases that is used to group rows that have the same values in specified columns into aggregated data. Essentially, it's a way of consolidating similar data into a single, summarized record.

While the Hasura graphql-engine's auto-generated API is reasonably expressive, it doesn't support Group By requiring users to create views, functions, or Hasura native queries to address use cases that require Group By capabilities. While this is suitable, there are several drawbacks such as requiring DDL privileges, extra effort, and added complexity.

Proposed Solution

An extensive explanation of the proposed Group By support can be found at the following link.
RFC: Group By Support (Flat Approach)

Discussion

We invite members of the community to review the proposed solution for GroupBy and provide feedback here.

  • Technical Validity: Are the technical details of the proposal sound and feasible? Does the proposal solve the problem it is intended to address?
  • Use Case Coverage: Does the proposed solution effectively address the real-world use cases you encounter?
  • Impact Analysis: What do you anticipate will be the impacts of the proposed changes on different aspects of the system such as performance, security, and usability?
  • Alternative Solutions: Are there alternative solutions that haven't been considered in this RFC? Can you suggest different approaches or existing solutions in other projects that could be effective?
  • Risks and Drawbacks: What potential risks and drawbacks do you see associated with the proposed changes? What are the implications if something goes wrong?
  • Implementation Challenges: Do you foresee any challenges or obstacles in implementing the proposed changes? How could these be addressed?
  • Clarity of Presentation: Are all aspects of the RFC clear to you? Are there any areas that need more explanation or detail?

Your feedback on these areas will be invaluable in helping us refine the proposal and make an informed decision about the future direction of our project.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions