[TerryN]

Haha. Wow, I didn't realize I was about to single-handedly split the ticket with my vote. 😀

I'm trying to see myself working this way, but just can't because of the current behavior of having all tabs in a connection be locked up while any one of them is executing. 🙁

I'd just open another connection. Using Ctrl-Tab it's a breeze to switch between them–actually easier than switching between tabs, I think. Since under what you're proposing, those multiple queries couldn't be executing simultaneously anyway, presumably your work pattern isn't such that they'd be returning data simultaneously if put in separate connections (though they'd be able to).

Are you limited to one connection by the server? Do you need them to share user variables? Or are you manually tunneling, so an additional connection is a hassle?

[TerryN]

'peterlaursen' wrote:

My concern is that if some user presses ENTER after entering a value it will start retrieving data again. And that may take time. So personally I think only the 'refresh' button should fetch data.  But let us see what developers think.  There may also be some official or 'de facto' standard in this respect.

As someone who works with a lot of slow queries (and not for lack of optimization 😉 ), my thoughts immediately went to unintended refreshes too. Some people who frequently edit database records (in some interfaces) might have a habit of pressing ENTER to commit changes to text fields. Then again, you might not do it unless you were finished making changes, so… maybe when they meant to also change the other box they wouldn't do it?

I like the idea, personally, but I have no such habit. As long as it's not accidentally implemented in such a way that it's triggered by the box merely losing focus! 🙂

[Author]

Posts