screenshot please

Here we go:

When site is up to date, you'll see this:
http://drupal.org/files/issues/update_form_enhancement_site_up_to_date.png

When there're some pending updates, a couple of collapsible fieldset are used. Here's an example showing fivestar module needs updates:

http://drupal.org/files/issues/update_form_enhancement_site_pending.png

I wasn't aware of that issue for D7. I have never had the need to review past updates, since I just wanted to "touch" the UI, I thought it would be enough hidden unnecessary information behind collapsed fieldsets. And these days I'm using update.php a lot, following CCK and Views related updates for two different projects that use a bunch of modules (meaning update.php renders a lot of selection boxes), so I did this module for me and thought it would be nice to upload here for other update.php "victims". :)

It looks great that this is now being addressed in core D7. It seems to me it's getting a good direction. Though, when you're about to run update.php, I think you just need that. I don't think it's a good place to display a lot of information about schema updates. When you are at that point, you have already updated the module files, and you shouldn't do that if you haven't read release notes, made backups, etc.

I mean, I would simplify update.php as if it was just a tool to perform a task in the middle of a process where it is supposed that you already know what you're doing. So the tool to update schemas ought to be as simple as possible, IMHO.