tag:blogger.com,1999:blog-4677316190423110840.post5515977603216185626..comments2023-08-25T13:49:41.382+02:00Comments on Software Engineer Thoughts: A better view? I do not think so.Paweł Baruthttp://www.blogger.com/profile/16867021334037413869noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-4677316190423110840.post-77491191833028188062006-10-20T22:13:00.000+02:002006-10-20T22:13:00.000+02:00Noons, thanks for your comment. I also use views, ...Noons, thanks for your comment. I also use views, but I tend to not give direct access to views. I rather tend to return ref cursors that are in fact based on views. That way you have more control over your code and API functionality. And you control on database side how query is constructed, and how executed. Front-end developers usually have too superficial knowledge about database stuff.<br />Today <a href="http://www.petefinnigan.com/">Pete Finnigan</a> has interesting entry on the same topis <a href="http://www.petefinnigan.com/weblog/archives/00000940.htm">Using procedures to access data only</a>. I agree with him, that dual access can be harder to control.Paweł Baruthttps://www.blogger.com/profile/16867021334037413869noreply@blogger.comtag:blogger.com,1999:blog-4677316190423110840.post-54785837211078301782006-10-17T02:35:00.000+02:002006-10-17T02:35:00.000+02:00My personal preference is for a mix of the two tec...My personal preference is for a mix of the two techniques.<br /><br />I tend to favour your approach of auto-generation of a PL/SQL "wrapper" package for each table and/or business function, depending on the application.<br /><br />But views are extremely attractive to provide isolated "windows" into a schema. <br />In fact, in some cases I've used views and "instead of" triggers as a way to transform a given schema into another. <br />For example, to evolve an underlying schema into a more normalized one, while keeping the previous access code the same. <br />Minimal intrusion was the goal in that case.<br /><br />Anyways: just a few ideas.Noonshttps://www.blogger.com/profile/07694829378563989648noreply@blogger.com