Re: why administrator refuse to give permission on PLUSTRACE

On 2007-11-03 06:30, DA Morgan <damorgan_at_psoug.org> wrote:
> But lets give you an opportunity to test those developers around you to
> see how good they really are.
>
> What would you do if the stored procedure "test" was identified as the
> issue?

If that procedure has been identified as "the issue" (whatever "the issue" is and however that has been determined) most of the forensic work has already been done. The rest is fixing the problem which is the developer's job.

> CREATE OR REPLACE PROCEDURE test IS
> BEGIN
> FOR r IN (SELECT * FROM parent)
> LOOP
> r.part_num := r.part_num * 10;
> INSERT INTO child
> VALUES
> (r.part_num, r.part_name);
> END LOOP;
> COMMIT;
> END test;
> /

I realize of course that your example isn't meant to do anything useful, but that's what makes it unrealistic. Because if I find a procedure called "test" which does what the procedure above does, and which appears to be "the issue", the first questions I am going to ask are: What is this supposed to do? Is it doing that? Is it needed at all? If it is, when is it needed? Why is it not documented? Only after answering these questions and establishing that the procedure is indeed useful and needs to be called as often as it is (which includes documenting it and probably renaming it to something more descriptive) am I going to look into how to make it faster. (At least in an ideal world - if the users are breathing down my neck I might try the obvious optimization first and then do it right).

        hp

-- 
   _  | Peter J. Holzer    | It took a genius to create [TeX],
|_|_) | Sysadmin WSR       | and it takes a genius to maintain it.
| |   | hjp_at_hjp.at         | That's not engineering, that's art.
__/   | http://www.hjp.at/ |	-- David Kastrup in comp.text.tex