Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • I think one should write queries against views and not against tables. I tend to think people who use query builders tend not to write views or ask DBAs to create them for them. In doing so they don't leverage all the power of the RDBMS. Commented Feb 2, 2016 at 1:38
  • 1
    @user61852: Other than possibly some security and filtering for free, what can queries against views provide that queries against tables cannot also provide? Commented Feb 2, 2016 at 5:15
  • 4
    @RobertHarvey The same thing that programming to interfaces instead of concrete classes. Decoupling and flexibility. The design of the underlying tables could chance as long as the "contract", the view, remains "simulating" the same columns as ever. Commented Feb 2, 2016 at 8:35
  • @user61852 Fair enough. Commented Feb 2, 2016 at 15:36
  • @RobertHarvey I turned that into an answer. Commented Feb 2, 2016 at 15:39