The fix for issue #11314 resolved this issue, too.

In ADS 19 beta 30, I tested this scenario in Paraccel 5.1

Used same script given in main issue description.

1.When we rename function name in Alter Function UI and try to alter,  we are still getting error message.

2.If we see in Preview SQL tab, SQL is generated as 

Pls confirm at your end.

Function name is not renamed, hence reopening this issue.

The suggestion to remove the schema name from the ALTER FUNCTION statement only works if the schema is "public".

Take a look at the sample script in the issue description. The schema is "test_schema". If we don't specify the schema name in the ALTER FUNCTION statement, it'll complain that the function doesn't exist.

I've fixed FunctionDialog to do a DROP FUNCTION first and then CREATE OR REPLACE FUNCTION for ParAccel when the function is renamed.

@jenny: is this done for any other DBs? Specifically, issuing a DROP FUNCTION first?

The fix is for ParAccel only. [SP] Understood. But do we do the DROP FUNCTION for any other DB when the user chooses ALTER FUNCTION action in UI? I ask b/c it is possible that the DROP FUNCTION succeeds but thte CREATE OR REPLACE FUNCTION fails

[Jenny] Take a look at FunctionDialog, line 709, where ScriptFunction.scriptDROP is called for DBs that don't support CREATE OR REPLACE FUNCTION, ALTER FUNCTION, or REPLACE FUNCTION syntax.

Since the ALTER FUNCTION RENAME syntax doesn't work correctly for ParAccel, we can disable editing of the function name in the Function Dialog UI.

I've reverted my previous code changes.

We've decided to disable editing of the function name in the Alter Function dialog for ParAccel. I've checked in this code change.

Verified in ADS 19 beta 31 build.

For Paraccel DB, In Alter Function UI, renaming function name is disabled now.