Re: Corporate Acceptance of Creating Views ?

Think of a view like a subroutine.

If you use the code only in one program, No view. If you use the code in more than one program use a view. You change the view one time, and test each program.

With the no view rule, you increase your maintenance load by having to make changes in all programs and test each program.

jane (janeyiu_at_optonline.net) wrote:
: Is it true that in general corporate enviornment, the use of Views is
: discouraged ? even frowned up ?

: I was working with this "seasoned" developer on developing reports, I am new
: to the Oracle enviornment
: and she insisted that I should NOT use views if at all possible, preferablly
: not at all.

: "You should be able to get all the data you need with straight SQL...even if
: it have to go for pages !"
: "...you are creating yet another dependency...it's another object that has
: to be maintained !......"

: The thing was with tools like Crystal Reports, it does not handle manual SQL
: very well (requires
: a separate file to store the query)

: Is this true ? Was she full of bs ?

: thanks
: jane

--
While Alcatel may claim ownership of all my ideas (on or off the job),
Alcatel does not claim any responsibility for them. Warranty expired when u
opened this article and I will not be responsible for its contents or use.