Feature requests for version 9

Roeland

Member³
Hi,

Maybe a bit late, but I was hoping that the next version of PLSQL Developer have at least this enhancements:

- Recognizing a XMLType column and show the proper results instead of ''. And yes, I can use the GetClobVal, but that's cumbersome and only useful in a SQL window. Not when I'm testing some package methods that returns a cursor with xmltypes.

- Major upgrade for the grids. There are a lot of better grids in the world than the current outdated one. (And then I don't mention the issues that the current one still has after all this years...).

- Better support for Xml in general. eg: Codecompletion, editing?, validation?... And this bug fixed: XMLElement is empty?

Not very big issues I guess, so my expectations are very high,

Roeland

 
Compare User Objects between schema file for offline database.

We need this feature because we have remote access on our customer Dbs but we haven't a VPN access.
 
I hope PL/SQL Developer v9 will be able to handle Index Partitions, not just Table Partitions as currently. "Compare User Objects" should also be aware of them and distinguish those differences.
 
On the subject of partitions, it would be nice to have some more support for them than the current basic listing in the View/Edit screen. They need to be in the object browser so we can perform operations on individual partitions - view stats, truncate, exchange, drill down into subpartitions etc (we can some of this functionality ourselves using Browser Extender, but only if they are in the browser). The current listing isn't much help, to be honest.
 
While we're at it, there must be a stack of enhancement requests for the Code beautifier by now. It seems to have had only basic maintenance for the last decade. For example, after formatting I still have to add the spaces after my leading commas, pair up my DECODE arguments, remove the linebreaks in NVL and TO_DATE etc.
 
Indeed, the enhancements for the Code Beautifier didn't make it into Release 7, neither in 8. Another enhancement request which has been out there for a long time is proper column mode editing as in for example UltraEdit.
 
Sometimes I mix up the tools "Compare User Objects" and "Compare Table Data". The identical design of both makes that mistake easily possible. However when you just want to compare a whole schemas user objects and thought you had picked "Compare User Objects", but had picked "Compare Table Data" instead, you hardly can escape an endless cycle of comparisons. There should be some additional check and reassurance of PSD before starting to compare large numbers of tables with large numbers of rows. A somewhat different design of both tools would help avoid that confusion too before starting to compare.
Currently in this case you're pretty much forced to kill your PSD session to escape.
 
Back
Top