![]() | ![]() Products ![]() ![]() ![]() ![]() |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB Enhancement Requests and Suggestions » View Thread |
Messages 1 to 10 of 22 total |
![]() |
Thu, Mar 21 2013 4:52 PM | Permanent Link |
Barry | Here are a couple of minor EDBMgr suggestions:
1) When closing an *empty* SQL window, I still see the dialog "This is a new statement and has been modified. Would you like to save before closing?" - I don't see any point saving an empty SQL window. ![]() 2) It would be nice to have Find (Ctrl-F) work in the execution plan window so I can easily find the "Hint" in case I'm missing an index on one of the tables. I find that SQL with a lot of SQL joins generate a large execution plan and I may miss seeing the "Hints". 3) You could output the execution plan as HTML (using the same tabbed window - Popup Menu: HTML/Text output?) then mark up certain phrases like "Hint" in red colored HTML tags so it stands out better. This could also be used to call the user's attention to parts of the execution plan like if Misses are too high or Buffer Size is set too low etc.. Barry |
Fri, Mar 22 2013 3:30 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. ![]() | Barry,
<< 1) When closing an *empty* SQL window, I still see the dialog "This is a new statement and has been modified. Would you like to save before closing?" - I don't see any point saving an empty SQL window. ![]() I can't reproduce that here. Are you sure that you didn't at least modify the SQL a little before trying to close it ? << 2) It would be nice to have Find (Ctrl-F) work in the execution plan window so I can easily find the "Hint" in case I'm missing an index on one of the tables. I find that SQL with a lot of SQL joins generate a large execution plan and I may miss seeing the "Hints". >> Noted. << 3) You could output the execution plan as HTML (using the same tabbed window - Popup Menu: HTML/Text output?) then mark up certain phrases like "Hint" in red colored HTML tags so it stands out better. This could also be used to call the user's attention to parts of the execution plan like if Misses are too high or Buffer Size is set too low etc.. >> Noted. Thanks, Tim Young Elevate Software www.elevatesoft.com |
Sat, Mar 23 2013 10:47 AM | Permanent Link |
Dominique Willems | Tim Young [Elevate Software] wrote:
> << 2) It would be nice to have Find (Ctrl-F) work in the execution > plan window so I can easily find the "Hint" in case I'm missing an > index on one of the tables. I find that SQL with a lot of SQL joins > generate a large execution plan and I may miss seeing the "Hints". >> > > Noted. Would it be a lot of work to include a Find when viewing a text blob...? |
Sat, Mar 23 2013 5:53 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. ![]() | Dominique,
<< Would it be a lot of work to include a Find when viewing a text blob...? >> Already on the list - Roy asked for this a while back. I'll be picking up a new round of EDB Manager enhancements for the next minor release, so I should be able to include this one. Tim Young Elevate Software www.elevatesoft.com |
Sat, Mar 23 2013 6:50 PM | Permanent Link |
Dominique Willems | Tim Young [Elevate Software] wrote:
> I should be able to include this one. Awesome, as usual. ![]() |
Sun, Mar 24 2013 2:22 PM | Permanent Link |
Barry | << 1) When closing an *empty* SQL window, I still see the dialog "This is a
new statement and has been modified. Would you like to save before closing?" - I don't see any point saving an empty SQL window. ![]() <I can't reproduce that here. Are you sure that you didn't at least modify the SQL a little before trying to close it ?> Sure did. Here are the steps to reproduce it: 1) Open a new SQL window and enter any SQL statement and execute it: delete from tablex and execute it 2) I then select all of the SQL text (if it updates or deletes rows) and delete it so I don't accidentally execute it again. But I leave the tabbed window open because I may want to reuse it for entering another SQL statement. 3) If you later try and close the empty SQL window, it then prompts you if you want to save it. My point is, if the SQL window is empty, why would anyone want to save it? Barry |
Mon, Mar 25 2013 12:31 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. ![]() | Barry,
<< 3) If you later try and close the empty SQL window, it then prompts you if you want to save it. My point is, if the SQL window is empty, why would anyone want to save it? >> Because they accidentally deleted all of the text ? I'm not being coy here, there is the possibility that someone did something accidentally, and I can't really assume that this *isn't* the case, so I have to err on the side of caution. Tim Young Elevate Software www.elevatesoft.com |
Mon, Mar 25 2013 1:01 PM | Permanent Link |
Roy Lambert NLH Associates ![]() | Tim
><< 3) If you later try and close the empty SQL window, it then prompts you >if you want to save it. My point is, if the SQL window is empty, why would >anyone want to save it? >> > >Because they accidentally deleted all of the text ? >I'm not being coy here, there is the possibility that someone did something >accidentally, and I can't really assume that this *isn't* the case, so I >have to err on the side of caution. If they accidentally deleted all the text only a moron (ie me) would want to save the now empty window <vbg> Being more serious I suppose the idea is that they could click Cancel and ctrl-z to get the stuff back. Maybe what Barry should have suggested is just remove the save button, unless you want to give users the option of replacing a nice full file with an empty one. Roy |
Tue, Mar 26 2013 3:25 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. ![]() | Roy,
<< If they accidentally deleted all the text only a moron (ie me) would want to save the now empty window <vbg> >> Yes, but that's the point of the prompt - to indicate to the user that it was modified and that they need to make a decision. << Being more serious I suppose the idea is that they could click Cancel and ctrl-z to get the stuff back. >> Yes, and when it prompts them, it makes sure to make that SQL window visible so that they can *see* what they have/haven't done. Plus, remember that you can undo the text even after it has been saved. << Maybe what Barry should have suggested is just remove the save button, unless you want to give users the option of replacing a nice full file with an empty one. >> What if someone *wants* to save an empty SQL file, for whatever reason ? You guys are assuming too much here. About the only reasonable thing I can do is to put in a prompt when the user tries to save an empty SQL statement using the Save button directly. That will prevent overwriting a file with the empty SQL by accident. Tim Young Elevate Software www.elevatesoft.com |
Wed, Mar 27 2013 12:34 AM | Permanent Link |
Barry | Tim,
<Yes, and when it prompts them, it makes sure to make that SQL window visible so that they can *see* what they have/haven't done. Plus, remember that you can undo the text even after it has been saved.> I didn't realize there was an Undo feature in your SQL window. Your logic makes sense now. (I never had to use the Undo because I never make a mistake. LMFAO) <What if someone *wants* to save an empty SQL file, for whatever reason ? You guys are assuming too much here. About the only reasonable thing I can do is to put in a prompt when the user tries to save an empty SQL statement using the Save button directly. That will prevent overwriting a file with the empty SQL by accident.> Nah, I think it works ok as it is, now that you've explained you have an Undo. Barry |
Page 1 of 3 | Next Page » | |
Jump to Page: 1 2 3 |
This web page was last updated on Wednesday, August 14, 2024 at 07:31 PM | Privacy Policy![]() © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? ![]() |