Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement grouping options for the URI type #414

Closed
Tracked by #246
kgodey opened this issue Jul 16, 2021 · 0 comments · Fixed by #1342
Closed
Tracked by #246

Implement grouping options for the URI type #414

kgodey opened this issue Jul 16, 2021 · 0 comments · Fixed by #1342
Assignees
Labels
ready Ready for implementation type: enhancement New feature or request work: backend Related to Python, Django, and simple SQL

Comments

@kgodey
Copy link
Contributor

kgodey commented Jul 16, 2021

Problem

Users may want to group records that contain URI types by first character, URI scheme, or URI host of the column's value.

We need to provide the ability to group by these.

Solution

We should extend our record grouping mechanism to accept first character, URI scheme, or URI host as grouping parameters for columns of URI types.

This involves:

  • Implementing the grouping in the backend
  • Updating the /api/v0/databases/<id>/types/ endpoint to store available grouping on this type

Additional context

@kgodey kgodey added needs: unblocking Blocked by other work type: enhancement New feature or request work: backend Related to Python, Django, and simple SQL work: database labels Jul 16, 2021
@kgodey kgodey added this to the 07. Initial Data Types milestone Jul 16, 2021
@kgodey kgodey added ready Ready for implementation and removed needs: unblocking Blocked by other work labels Feb 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready Ready for implementation type: enhancement New feature or request work: backend Related to Python, Django, and simple SQL
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

2 participants