re: Explain Postgresql Views Like I'm Five VIEW POST


I use views, and create views frequently. Not necessarily in postgres. I've used views mostly to do joins from various tables and do basic calculations across joined fields. Usually then called and stored in another table that others on my team have permissions on. They don't need permissions on the hundreds of tables on the various schemas. As was said think of views as a saved sql statement.


One thing I used to use views for was on an unknown schema to join everything I could find together into one enormous pile of data, so I could get an overview of what was going on quicker. I wouldn't use these monsters for anything apart from that though!

code of conduct - report abuse