procedure with no parameters - tabs
| User, date | Message |
|---|---|
|
Written by BubikolRamios
2 months ago Category: Feature discussion 273 posts since Thu, 14 Jan 10 |
1. have a normalized table, wich I convert to denormalized often by left click on proc/run routines() 2. hence the number of opened query tabs builds up enormously (-: a) no point to put "call proc ()" into new query tab if proc has no parameters. b)Never understood the sort order of query tabs. It is a mess. One time query#2 is at start (left top) position next time totaly elsewhere ..... I think these (query tabs) should be ordered as they were created, preseving 'data tab' and such at start of tab list. |
|
Written by BubikolRamios
2 months ago 273 posts since Thu, 14 Jan 10 |
also, there is no 'close all query tabs'. And it is needed. |
|
Written by ansgar
2 months ago 3949 posts since Fri, 07 Apr 06 |
a) where should a procedure and its result be displayed if not in a query tab? There is no other place where HeidiSQL can display a result. b) The sort order of query tabs is fine, probably you just did not fully get it: All tabs keep their position from when they were created. You have the very first, non-closable query tab (1), and when you open a new one it gets named "#2", then #3, #4 and so on. If you load a file into any query tab its name is renamed to the filename in it. The numbers are still valid, just check it by counting from left to right. I must admit that if you open lots of tabs it tends to get overcrowded. But you should not blame HeidiSQL only for that - you have opened these tabs. A "close all query tabs" menu could be fine, but I tend to keep rarely used menu items and buttons away from HeidiSQL, to keep it simple. |
|
Written by BubikolRamios
2 months ago 273 posts since Thu, 14 Jan 10 |
a) proc like "procedure()" with no parameters produces nothing, did not check, but I think even if final stuf in it is select sentence it does not spit anything into query resultset box. b) sample, clickeq query 3 (set focus) on upper image, and while I had query 10 where it was it wend on total different place. I think tabs should stay where they are, no need to shift them around when they get focus. 
|
|
Written by BubikolRamios
2 months ago 273 posts since Thu, 14 Jan 10 |
The upper image is actualy nice one, query 10 moves one up, but could be also anywhere else ..... |
|
Written by ansgar
2 months ago 3949 posts since Fri, 07 Apr 06 |
Ah, get it now. Well, that's done automatically by Windows, and it's impossible not to do that when having tabs in more than one row. When you click #3 it has to be highlighted/focused. That happens along with moving the whole tab row into the foreground. |
|
Please login to leave a reply, or register at first. |