Re: Why use Pro*C for spooling result sets to flat files when you can do the same thing in SQL*Plus?

Thanks for all of the responses.

It seems that they have more Pro*C-savvy developers that are less savvy with
SQL*Plus. After thinking about the situation and what really matters to me
at work politically and outside work personally, I told the lead DBA this
morning that I would learn Pro*C. I'll pick and choose my battles once I
have gained some ground here. At least I have this venue to freely express
my professional interests and insights.

Thanks again!
Bill


On Thu, Sep 2, 2010 at 10:31 AM, Bill Ferguson <wbfergus@xxxxxxxxx> wrote:

> On a slightly common note, but probably more off subject, when I first
> started with the Governemnt back in 1988, all of our reports were
> written in Pro*FORTRAN. What a nightmare that was, especially on a
> HP-UX machine and having to recompile everything whenever Oracle or HP
> came out with new versions (or library patches). Pro*FORTRAN was
> chosen because the reporting requirements (layout, computations,
> multiple tables in the same report, looping, etc.) couldn't be handled
> by SQL*Plus.
>
> At least now I've finally got them all re-written in PL/SQL packages.
>
>
> --
> -- Bill Ferguson
>

Other related posts: