Hi there,

Just a minor thing that I've noticed several times that can be annoying and could be fixed.

If you do a query in the SQL Window in PL/SQL Developer 7 and now 8 and it fetches only the first 10 (for example) rows in the database it sizes the columns in the results grid based on the content of those first 10 rows.

If the content of those first rows fits horizontally on the screen nicely then all is good. In particular there is no need to display a horizontal scroll bar along the bottom of the screen to show all the results because they fit on the screen nicely.

If the 'Fetch Next Page' button is clicked some further rows are fetched. If the results differ content wise from those in the first rows fetched then the row widths in the results grid are resized to be larger. If this goes over the width of the screen then I would expect that the horizontal scroll bar would be displayed at this point so the results can be scrolled into view. Unfortunately it isn't, which makes it difficult to view the results.

This is inconsistent with the display of the horizontal scroll bar immediately if the first screens results go over the width of the screen.

The workaround is to click into the results grid after the 'Fetch Next Page' and tab out to see the results.

Just a minor glitch in a great product.

Thanks,
Pete.

I cannot immediately reproduce this, but we'll check it out.

In the preferences>SQL Window, what number do you have in the Records Per Page? Do you have it Automatically determined, or Fixed...or All?

It is set to the default 'Automatically Determined'. I like it that way as it uses the results grid height to determine the number of records to fetch.