I've downloaded the latest trial available (6.0.5) a few days ago and gave it a try. Here's what immediately popped up for me:
1. Compile invalid objects tool.
This one doesn't recompile any objects named in mixed case or starting with some illegal character (such names can be created by surrounding them in double-quotes.) Though not common in Oracle, some objects (namely Java classes/sources) are usually named in mixed case and these fall out of recompilation scope in PL/SQL Developer. Would be proper to surround all object names with double-quotes in ALTER xxx COMPILE commands.
2. Java Sources list.
This list shows class names in short format, which is not very readable and is only there to fit the standard object name length constraint of 32 characters. DBMS_JAVA.LONGNAME() function can be used to retrieve the complete class name. Oracle recognizes both short and long names in CREATE JAVA SOURCE command, so having all names expanded is preferred. Would be nice if you'd change your query for Java source names to use this function.
3. Java source editor.
When it opens a Java source, it automatically converts the short source name (see 2. above) to lowercase and doesn't surround the name with double-quotes. Unless one edits the name manually, the object will be created with wrong name instead of original object replaced and recompiled, or won't be created at all if the name is a collapsed long name (in form of "/_ClassName".) You must keep the original case and surround the name with double-quotes for Java source editor to work as it's supposed to.
Would be very nice to see these issues fixed in some maintenance release soon. Having these fixes in place may influence our management's decision to license this awesome product towards "yes" (but then again, maybe not...)
TIA,
Bob.
1. Compile invalid objects tool.
This one doesn't recompile any objects named in mixed case or starting with some illegal character (such names can be created by surrounding them in double-quotes.) Though not common in Oracle, some objects (namely Java classes/sources) are usually named in mixed case and these fall out of recompilation scope in PL/SQL Developer. Would be proper to surround all object names with double-quotes in ALTER xxx COMPILE commands.
2. Java Sources list.
This list shows class names in short format, which is not very readable and is only there to fit the standard object name length constraint of 32 characters. DBMS_JAVA.LONGNAME() function can be used to retrieve the complete class name. Oracle recognizes both short and long names in CREATE JAVA SOURCE command, so having all names expanded is preferred. Would be nice if you'd change your query for Java source names to use this function.
3. Java source editor.
When it opens a Java source, it automatically converts the short source name (see 2. above) to lowercase and doesn't surround the name with double-quotes. Unless one edits the name manually, the object will be created with wrong name instead of original object replaced and recompiled, or won't be created at all if the name is a collapsed long name (in form of "/_ClassName".) You must keep the original case and surround the name with double-quotes for Java source editor to work as it's supposed to.
Would be very nice to see these issues fixed in some maintenance release soon. Having these fixes in place may influence our management's decision to license this awesome product towards "yes" (but then again, maybe not...)
TIA,
Bob.
