2023-07 backend fixes¶
Name: 2023-07 backend fixes Status: In progress Review status: Approved
Team¶
Role | Assignee | Notes |
---|---|---|
Owner | Dom | |
Contributor (backend review) | Mukesh | Reviews backend code |
Problem¶
Time for some fixes!
Kriti compiled a list of minor backend issues in order of importance:
Remove the lazydict dependency #2960(since fixed)- Add support for
citext
column type #2959 Does not work on windows #2961(should be considered part of the removing sqlalchemy theme)- Demo users should only see their own database #2983
- StatementError when using the Record Selector to search by a partially-entered UUID #2724
- Fix API handling of multi-column UNIQUE and PK columns #2245
- Incorporate field name into error messages when relevant · Issue #1370
- Keep
today
astoday
in column default value · Issue #2754
I also created this issue to compliment the one for implementing citext
, since the originating bug report reported both of these types being unsupported and that blocking the reporter’s use case: Add support for point
column type #3007.
Kriti later added two issues to the list, saying they’re high-priority:
Cannot import large csv tables · Issue #2995 · mathesar-foundation/mathesar(discovered that the bandaid fix is frontend work, and the wholesome fix requires a lot of UX work)- Make permissions requirements clear for gunicorn user · Issue #3013 · mathesar-foundation/mathesar
Solution¶
Will start with block-prone issues. If or when I am blocked on any of these issues, I will work on the block-proof issues. Once block-prone issues are resolved, I will work on the remaining block-proof issues. If I were to do it the other way around, I’d risk being blocked with nothing to do.
Block-prone issues¶
Issues that likely need coordination with others.
I expect each of these to take roughly 3 days to complete.
- Fix API handling of multi-column UNIQUE and PK columns #2245
- Incorporate field name into error messages when relevant · Issue #1370
- Keep
today
astoday
in column default value · Issue #2754 - Support unknown Postgres types · Issue #3024 · mathesar-foundation/mathesar
Note on progress tracking¶
This document is not meant to track progress or updates to the plan. See the meta issue for that.
Block-proof issues¶
Issues that likely do not need coordination with others.
I expect each of these to take roughly 1 day to complete.
- Add support for
citext
column type #2959 (might be superseded by #3024) - Add support for
point
column type #3007 (might be superseded by #3024) - Demo users should only see their own database #2983
- StatementError when using the Record Selector to search by a partially-entered UUID #2724
- Make permissions requirements clear for gunicorn user · Issue #3013 · mathesar-foundation/mathesar
Time budgeting and progress estimation¶
I included rough estimates of how much time each issue should take. That will be usable as a guide on whether I’m on track.
The project budget is 20 days (4 weeks). Current estimate of total time required to submit PRs for above issues is 17 days (4 block-prone issues 3 days each, plus 5 block-proof issues 1 day each). 3 days buffer time.
Risks¶
- Finishing the tasks too early
- The prefered risk, since I can then pick up additional work
- Not finishing the tasks in time
- The worse risk, since not finishing in time will either leave work unfinished or interfere with the break period (and/or next cycle)
Resources¶
Timeline¶
This project should take 4 weeks.
Date | Outcome |
---|---|
2023-07-10 | Work starts |
2023-07-21 | Half-way mark (50% of work should be done) |
2023-08-02 | Buffer time starts |
2023-08-07 | Work ends |