-
-
Notifications
You must be signed in to change notification settings - Fork 320
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.
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
Query Builder and Views design #442
Comments
@kgodey One problem is going to be that if the purpose for having views is to be able to put a table back together that's been normalized into its constituent atoms, this will fall outside of what PostgreSQL will be able to deal with automatically, w.r.t. editing records. Note from the docs:
This means we won't be able to compose an automatically-updatable view from multiple tables. We would be able to compose one from a select on a single table under some circumstances. Off the top of my head, some uses for which this makes sense are:
|
@mathemancer That makes sense. I'd like us to build out the product a little more before we decide whether we need to provide functionality to update views that don't meet the PostgreSQL definition of updatable. I'll create an issue for it but put it in "future" for now. We can reevaluate when to schedule it in a few weeks. Edited to add: |
Another quick note about views: When implementing, note that they do have OIDs (and are available the same way as tables in the |
Although we are doing this feature in Cycle 3, this ticket no longer covers accurate design requirements, so I'm going to close it. |
Mathesar should support Postgres views. This is a meta-issue to structure all of the work needed to support that functionality. We will complete this work in milestone Working with Views.
Please see the following more information about views and queries:
Issues
Issues directly related to queries and views:
Issues supporting or depending on queries and views:
Previously created issues that were folded into other issues above:
The text was updated successfully, but these errors were encountered: