I mentioned that some time ago, but meanwhile I ran into big problems
with this issue and I would like to discuss it once more:

1. Right click a procedure in the tree and chose "Alter Function"
2. Edit the code in the sql-editor and click OK.
3. Supposed you have a mistake in your code: a message pops up and
offers to edit the wrong code.
4. Correct the wrong code and execute the statement.

Now the problem. The tree is *not* refreshed automatically. Thus: if you
forget to refresh it manually and edit the same procedure again in the
same session, you will edit the old code before your last changes.

I think the tree *must* be refreshed after a change by default. I know
that this can take some time with many entries, but it's just too
dangerous not to refresh it.

A simple workaround could be to refresh just the selected
procedure/function *before* opening the sql-window. How about that?

Regards Uli

I agree, I have almost done the same thing with views and procedures, i.e.

Have version 1.
Make change (version 2).
Think "ah change wasn't quite right, need to change again"
Grab SQL from tree
Make change ... (version 3)

... but you have changed version 1 -> version 3, not version 2 -> version 3!!!

I have 200 line View where I did that ... (

>>A simple workaround could be to refresh just the selected
>>procedure/function *before* opening the sql-window. How about that?

DEFINITELY: SQL opened by ALTER / EDIT form must be a live call .... not a canned result that may be old!

Uli,

<< A simple workaround could be to refresh just the selected
procedure/function *before* opening the sql-window. How about that? >>

That sounds workable.

--
Tim Young
Elevate Software
www.elevatesoft.com