Implement grouping options for money types

[kgodey]

Problem

We need to ensure that records that include columns of all Money types support range based grouping just like Number types via the API. Please see #384 for the implementation details.

We should be able to reuse the implementation for Number types here.

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

• Please see these PRs for code related to grouping:
  • Record grouping #315
  • Fix grouping counts #353
• We're using our fork of sqlalchemy-filters to provide filtering. See: https://github.com/centerofci/sqlalchemy-filters.
• This issue is blocked by Implement range based grouping for numeric types. #384
• This issue is also blocked by:
  • Backend work for Mathesar money custom type  #417
  • Handle MONEY data type in the backend. #420
• Update filtering issues to cover storing filter/group information in the backend. #557 provides some context on storing groups.

[Aditramesh]

@kgodey can i work on this?

[kgodey]

@Aditramesh This is a really old issue and I'm not sure how valid it is. Please check to see if money data types support all the same grouping types as number data types – if they don't, then you can work on it.

[Aditramesh]

@kgodey i can try doing that but if there is an issue which has higher priority and if you think I can solve it ,can you assign that to me ?

[kgodey]

@Aditramesh I don't have any issues that I can think of right now. We will probably have more issues in around two weeks. The core team is busy with preparing for our initial release right now, so we haven't had much time to go through our issues recently.

[Aditramesh]

Understood,then I will try to work on this ,thanks @kgodey

[Anish9901]

Unassigned due to inactivity.

[Aditramesh]

@Anish9901 i couldnt work much on this issue in the last two weeks but i have made some progress and i want to continue working on it,could you reassign this ?

[Anish9901]

Please create a PR @Aditramesh and I'll reassign the issue to you.

[kgodey]

Closing this, too old, requirements are out of date. We can create a new issue if we need this functionality in the future.