Support for editing the structure of a database view

[kgodey]

The Mathesar UI should allow users to edit the structure of an existing database view.

Scenario 1: The database view structure can be edited

1. The user clicks on a button or menu that allows them to edit the structure of a view.
2. We open the Data Explorer with pre-filled sections (see Design for visual query builder ("Data Explorer") #1065)
   1. There should be some indication that the data explorer was opened in response to a View editing request.
3. The user can edit the View structure and either save the view or save as a new view.

Error scenarios

• The user tries to remove a column that is a dependency for some other view or database object. The column cannot be removed.
• The view update fails in the backend.

Scenario 2: The database view structure cannot be edited

There may be some views whose structure cannot be edited. We should convey this to the user somehow, either by hiding the option or disabling it.

Additional context

• Blocked by design work:
  • Support for opening and interacting with a View #466
  • Design for visual query builder ("Data Explorer") #1065

[kgodey]

@dmos62 @ghislaineguerin @pavish @mathemancer @seancolsen @silentninja This issue has been updated and is ready for review. Please look through it and unassign yourself after you've added any feedback that you might have.

[ghislaineguerin]

@kgodey How would we handle this for views where we cannot edit the structure or know what the dependencies are? I'm assuming this will be read-only or not accessible?

[pavish]

@kgodey
This is a technical concern. I know this was discussed, I just want to re-iterate that when the structure is modified and the view is saved, the backend should handle deleting the old view and creating the new one with the same id, name and dependencies. As far as the clients are considered, the same view gets updated.

[mathemancer]

My concerns from the view creation discussion still apply. Other than that, I have nothing to add for this issue.

[kgodey]

@kgodey How would we handle this for views where we cannot edit the structure or know what the dependencies are? I'm assuming this will be read-only or not accessible?

@ghislaineguerin Yes. I added an additional scenario for it above.

@kgodey This is a technical concern. I know this was discussed, I just want to re-iterate that when the structure is modified and the view is saved, the backend should handle deleting the old view and creating the new one with the same id, name and dependencies. As far as the clients are considered, the same view gets updated.

@pavish Yes, this is how it will be.

[kgodey]

Although we are doing work related to this in Cycle 3, this ticket no longer covers accurate design requirements, so I'm going to close it.