#4 Source lookup for stored procs can be better, but is ok

[Gregory Golberg]

This is a placeholder for a bug/feature request
regarding the editor of stored procs.

As it is, it's good enough and low priority, IMHO.

Because:

1. It does not allow breakpoints, but planting
a breakpoint in Java at a call to Statement.execute()
(or equivalent) is good enough. It's good enough
because it's not that most stored procs are that long
that stepping through to the desired line from
the execute() call is so much of a pain.

2. It does not allow evaluation, but variables
and values can be seen in the Variables view of the
Debug perspective. That should be good enough;
complex expressions are as rare as very long
procs we decided are good enough (see #1).

As long as the most useful issue - hot replace
(http://sourceforge.net/tracker/index.php?
func=detail&aid=1497252&group_id=150446&atid=777815)
is addressed, this is all low priority but
good to track.