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.

Sign up for GitHub

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

Jump to bottom

[META] Architectural overhaul #3516

Open
11 of 23 tasks
mathemancer opened this issue Mar 27, 2024 · 0 comments
Open
11 of 23 tasks

[META] Architectural overhaul #3516

mathemancer opened this issue Mar 27, 2024 · 0 comments
Assignees
@mathemancer
Labels
affects: architecture Improvements or additions to architecture needs: backend approval The backend team might not agree on whether this makes sense for the codebase needs: frontend approval The frontend team might not agree on whether this makes sense for the codebase needs: requirements The problem is clear and worth solving, but we're not yet sure of the best solution type: meta List of related issues. Not meant to be worked on directly. work: backend Related to Python, Django, and simple SQL work: db-layer Related to SQL or PL/pgSQL work: frontend Related to frontend code in the mathesar_ui directory
Milestone
Beta

Comments

@mathemancer
Copy link
Contributor

mathemancer commented Mar 27, 2024 •
edited by seancolsen

Problem

The current back end has problems with performance and complexity stemming from keeping and maintaining state about DB-layer objects in the Mathesar web service (specifically in Django models maintained by that service). This meta issue will track the work for that project.

Tasks
Beta Give feedback
  2. Get testing for RPC functions organized and set up. #3518
    3 of 3
    ready type: maintenance work: backend
    Anish9901
  3. Create new RPC endpoint #3519
    ready type: maintenance work: backend
    mathemancer
  4. Remove demo code #3531
    affects: technical debt ready
    mathemancer
  5. Remove unused API docs cruft #3540
    affects: dx ready type: maintenance work: backend work: documentation
    mathemancer
  6. Remove Debian packaging pieces #3545
    affects: technical debt ready work: installation
    mathemancer
  7. Connections RPC front end #3543
    pr-status: review
    pavish
  8. Remove E2E testing infrastructure pieces #3548
    Anish9901
  10. Implement stub function to get DB connection during development #3549
    ready type: maintenance work: backend
    mathemancer
  12. Migrate columns APIs to RPC #3570
    1 of 6
  13. Migrate tables APIs to RPC #3575
    0 of 9
  14. Migrate schemas APIs to RPC #3593
    0 of 6
  15. Migrate constraints APIs to RPC #3594
    0 of 5
  16. Migrate records APIs to RPC #3592
    0 of 7
  17. Migrate explorations APIs to RPC #3595
    0 of 9

TODO: Many more tasks.

Additional context
@mathemancer mathemancer added type: enhancement New feature or request affects: architecture Improvements or additions to architecture work: backend Related to Python, Django, and simple SQL type: meta List of related issues. Not meant to be worked on directly. needs: requirements The problem is clear and worth solving, but we're not yet sure of the best solution needs: backend approval The backend team might not agree on whether this makes sense for the codebase needs: frontend approval The frontend team might not agree on whether this makes sense for the codebase work: db-layer Related to SQL or PL/pgSQL labels Mar 27, 2024
@mathemancer mathemancer self-assigned this Mar 27, 2024
@seancolsen seancolsen added this to the Beta milestone Mar 29, 2024
@seancolsen seancolsen removed the type: enhancement New feature or request label Apr 8, 2024
@seancolsen seancolsen mentioned this issue Apr 8, 2024
Closed
@seancolsen seancolsen changed the title [META] Backend overhaul [META] Architectural overhaul Apr 15, 2024
@seancolsen seancolsen added the work: frontend Related to frontend code in the mathesar_ui directory label Apr 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mathemancer mathemancer

Labels
affects: architecture Improvements or additions to architecture needs: backend approval The backend team might not agree on whether this makes sense for the codebase needs: frontend approval The frontend team might not agree on whether this makes sense for the codebase needs: requirements The problem is clear and worth solving, but we're not yet sure of the best solution type: meta List of related issues. Not meant to be worked on directly. work: backend Related to Python, Django, and simple SQL work: db-layer Related to SQL or PL/pgSQL work: frontend Related to frontend code in the mathesar_ui directory
Projects
None yet
Milestone
Beta
Development

No branches or pull requests
2 participants
@seancolsen @mathemancer