![]() In subsequent reads of a materialized view, the time taken to return its results would be much faster than a conventional view. Materialized Views #Ī materialized view is a form of view but it also stores the results to disk. We can prevent them from reading sensitive columns by excluding them from the underlying query. Instead of allowing a user direct access to a set of tables, we provide them a view instead. Views can restrict the amount and type of data presented to a user. For example, by looking at the name of the view transcripts, we can infer that the underlying query might involve the students, courses, and grades tables. Instead of guessing what a query is supposed to do, a well-named view can easily explain it. This is extremely useful for teams working with the same database. With views, we can give our query a name. The change will be applied to all applications using this view. With views, we can alter just the underlying query in the view transcripts. This would increase in the likelihood of errors and inconsistencies, as well as introducing a lot of effort for a developer. Without a view, we would need to go into every dependent query to add the new rule. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |