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

Backend spec for updating data in views that don't meet PostgreSQL "updatable" status #504

Closed
kgodey opened this issue Jul 28, 2021 · 3 comments
Closed

Backend spec for updating data in views that don't meet PostgreSQL "updatable" status #504

kgodey opened this issue Jul 28, 2021 · 3 comments
Labels
affects: architecture Improvements or additions to architecture priority: future Work for future consideration type: enhancement New feature or request work: documentation Improvements or additions to documentation

Comments

@kgodey
Copy link
Contributor

kgodey commented Jul 28, 2021 •
edited
Loading

Problem

We'd like to offer Mathesar users the capability to update data in views that don't meet the criteria for PostgreSQL "updatable" status. For instance, if a user splits a table into smaller normalized tables, they may want to see all their data in one place and edit their data from that view.

Proposed solution

We'll need to figure out how we could implement this and which types of views we could implement this for. This issue is just to do some experimentation and come up with a spec for how we could implement this in the backend.

Additional context

See discussions on:
@kgodey kgodey added work: documentation Improvements or additions to documentation type: enhancement New feature or request work: database needs: unblocking Blocked by other work labels Jul 28, 2021
@kgodey kgodey added this to the 26. Post-MVP milestone Jul 28, 2021
@kgodey kgodey mentioned this issue Jul 28, 2021
Closed
13 tasks
@kgodey kgodey added priority: future Work for future consideration affects: architecture Improvements or additions to architecture and removed needs: unblocking Blocked by other work labels Jul 28, 2021
@github-actions
Copy link

This issue has not been updated in 90 days and is being marked as stale.

@github-actions github-actions bot added the stale label Oct 28, 2021
@kgodey kgodey removed the stale label Oct 28, 2021
@github-actions
Copy link

This issue has not been updated in 90 days and is being marked as stale.

@github-actions github-actions bot added the stale label May 17, 2022
@kgodey kgodey removed this from the [v2] Future Consideration milestone Jun 1, 2022
@kgodey
Copy link
Contributor Author

kgodey commented Jun 2, 2022

We're going in a different direction with Views now, closing this.

@kgodey kgodey closed this as completed Jun 2, 2022
@kgodey kgodey reopened this Jun 2, 2022
@kgodey kgodey closed this as not planned Won't fix, can't repro, duplicate, stale Jun 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
affects: architecture Improvements or additions to architecture priority: future Work for future consideration type: enhancement New feature or request work: documentation Improvements or additions to documentation
Projects
No open projects
[NO LONGER USED] Mathesar work tracker
Archived in project
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kgodey