Recent content by BWendling

Hi, if numbers are formatted with thousand separator, this format should also be used in the column total row. That is, where I have large numbers very often which are difficult to read! e.g. 145443845.96 should be displayed as 145,443,845.96 GUI: For a more consistent user interface, in the...

Hi Marco, a little idea for tuning the user interface: In the SQL window, there should be a break button directly next to the button "Fetch last page". Thus, the buttons to start a fetch and to stop a fetch would be together in the same window. With screen resolutions growing, single window...

Hi Marco, number layout "formatted with thousand separator" should also be applied to column totals, e.g. sums. Sums are greater than regular cell values and would be much easier to read if printed with thousand separators, if that option is enabled. Regards,

Hi, when working with large numbers with 17 digits, even when whole integers, SQL window uses scientific notation and does not show anymore all digits. In companies, it's usual to work with large integer numbers (e.g. order numbers, part numbers, auto numbers) where all digits are important...

Hi, the user interface is inconsistent in having several places for very similar options, some permanent, some not - Show special characters (off by default) - Code folding (on by default) currently need to be switched on/off in every single window if one doesn't like the defaults. "Show...

Hi, any news about version 8? Will there be a beta version? I'd like to share my findings with you before release. Because I would love to buy a new PL/SQL Developer if it eventually correctly supports local partitioned indexes, all sorts of partitioning (see 11g) and some editor enhancements...

it will probably show up with full digits in Oracle SQL Developer. It's the same for "too many" mantissa digits which will be cut off in PL/SQL Developer, too. I wish PL/SQL Developer would always show all digits and never use scientific notation.

in , the word "allroundautomations" is cropped a pixel too small.

Hi, I had a similar experience shortly: After launching a query over night, on the next morning, I could see the first 100 rows (which would have given me a good indication), but when I clicked on the window, I got "not connected to Oracle" error and the so far retrieved results were gone.

Hi Marco, I tried version 7.1.4 because it should support showing special characters (space, CR/LF etc.). It's true, there is a function in the edit menu. But as far as I found out, it must be manually enabled in every new window. Is there a Preferences option to automatically enable "show...

Recently, I was requested to renew my PL/SQL Developer license. I'm a little embarrassed that there is still no support for essential Oracle features such as local (partitioned) indexes, subpartitioning etc. Actually, I didn't notice a big improvement in PLSD over the last year, so I'm...

I really wish to have a log of what I entered into the Test Windows, too. Is that so difficult? Just write a log file with all statements somewhere. Also, failed SQL window statements should also be logged or even recoverable. Thank you.

Normally it helps to update to the latest patchset. Which version are you on (v$instance)?

If you create a range partitioned index organized table, the "View SQL" function wrongfully places the "organization index" clause below the partitiong information. This clause belongs before the partitioning info. Example: create table TEST ( SORTID NUMBER(4), VALUE...

This is a confirmed bug in 7.0.1066. http://www.allroundautomations.com/ubb/ultimatebb.php?ubb=get_topic;f=3;t=002880