When to use database views and when not?

views database-agnostic
FerranB picture FerranB · Mar 10, 2009 · Viewed 30.2k times · Source

This question is about database views, not materialized-views.

Pros:

  • Query simplification.
  • Avoid repeat the same joins on multiples queries.
  • Avoid magic numbers.

Cons:

  • Hiding real queries (may be you are repeating joins).

What else?

Answer

Andy White picture Andy White · Mar 10, 2009

Pros: Allows you to change the underlying data structures without affecting the queries applications are using (as long as your view can hide the data structures)

Related questions

Attempt to present UIViewController on UIViewController whose view is not in the window hierarchy

Just started using Xcode 4.5 and I got this error in the console: Warning: Attempt to present < finishViewController: 0x1e56e0a0 > on < ViewController: 0x1ec3e000> whose view is not in the window hierarchy! The view …

Read More
Can we pass parameters to a view in SQL?

Can we pass a parameter to a view in Microsoft SQL Server? I tried to create view in the following way, but it doesn't work: create or replace view v_emp(eno number) as select * from emp where emp_id=&…

Read More
How to create EditText with rounded corners?

Is there any way to create EditText that has rounded corners?

Read More