Comments
Sort by recent activity
I agree that Prompt 3 is too invasive. I am constantly having to hit escape to close the box or backspace to erase things that I did not want.
Bagging this product as usless to me. Very disappointing as I was enthused by Prompt 2 and it really was an aid to speeding up my work.
Tim
Denver, CO / comments
I agree that Prompt 3 is too invasive. I am constantly having to hit escape to close the box or backspace to erase things that I did not want.
Bagging this product as usless to me. Very disappointi...
I have run into this problem also. How do you manually refresh the cache?
Tim
Denver, CO / comments
I have run into this problem also. How do you manually refresh the cache?
Tim
Denver, CO
Another example of hyper activity.
I am between single quotes and entering a date as a string value as follows:
EXEC prc_RptChangeRequest '12/1/2006'
If I pause while typing or even the brief pause when I get to the end of the string and the darn candidate box appears with no entries in it.
I agree with Alasdair. Prompt 2 was a great product that needed a little refinement.
Tim
Denver, CO / comments
Another example of hyper activity.
I am between single quotes and entering a date as a string value as follows:
EXEC prc_RptChangeRequest '12/1/2006'
If I pause while typing or even the brief pause...
I have experienced the same. In prompt 2 a snipped was inserted directly when I typed ssf <tab>. In prompt 3 the fuctionality is completely different. If I type ssf and then wait I get a candidate box that has SELECT * FROM in it and I can choose it by hitting enter. But if I type quickly (like I have a full day of work and feel I should have to key things and wait) and hit enter I am left with ssf and my cursor on a new line. If I instead hit space I get a candidate list but database items, not snippets.
All in all I think this functionality has gone from almost right to more work than it is worth.
Tim
Denver, CO / comments
I have experienced the same. In prompt 2 a snipped was inserted directly when I typed ssf <tab>. In prompt 3 the fuctionality is completely different. If I type ssf and then wait I get a candidate ...
Hope this does not come off as too cranky, BUT.
That is a pretty crappy answer in a forum that is titled "SQL Prompt 2". If I got that response from a representitive of a company it would probably encourage me to buy a competing product. If you (Red Gate, not personally) do not wish to answer questions or have input on Prompt 2 maybe you should eliminate the forum.
Tim
Denver CO
A loyal Red Gate customer / comments
Hope this does not come off as too cranky, BUT.
That is a pretty crappy answer in a forum that is titled "SQL Prompt 2". If I got that response from a representitive of a company it would probably ...
Thank you. Using the {} to bracket the ( and ) did the job as explained in the post.
Tim
Denver, CO / comments
Thank you. Using the {} to bracket the ( and ) did the job as explained in the post.
Tim
Denver, CO
OH MY GOSH!!
I now feel truly lost without my SQL Refactor. Guess I did not read the fine print as I was not expecting to lose the beta before the product was released.
The though of having to hand lay out my code and type out "SELECT * FROM " for 4 or 5 days is now so foreign and revolting. Please, please release on time. My license code is waiting.
Tim
Denver CO / comments
OH MY GOSH!!
I now feel truly lost without my SQL Refactor. Guess I did not read the fine print as I was not expecting to lose the beta before the product was released.
The though of having to hand...
An option for it to work or not work in comments would be a welcome adition in my mind.
Thanks,
Tim
Denver, CO / comments
An option for it to work or not work in comments would be a welcome adition in my mind.
Thanks,
Tim
Denver, CO
Andras,
Thank you for the explaination. I now understand how to make it work.
Another question. Why don't you layout the SQL for the proc according to the selected rules for Lay out SQL? Seems sort of crazy that the auto generated SQL is in a different layout that want I have specified. If I want to make my proc look as I wish I now have to take the second step of formatting. Sort of diminishes the value of a tool that is suppose to make me more efficient especially when the tool already has the second function.
Any input on the loss of the comment block? I have asked on the SQL prompt section about support for a comment block as an insert. Currently it crashes Prompt. Seems to be no one from Red Gate replying on that group.
Tim
Denver, CO / comments
Andras,
Thank you for the explaination. I now understand how to make it work.
Another question. Why don't you layout the SQL for the proc according to the selected rules for Lay out SQL? Seems sort...
Bart,
Thanks for the reply.
I have already bought my Prompt 3 license so I am waiting anxiously for it's introduction.
Any input on Auto Insert being case sensitive in recognizing the shortcut code when you use it, but not being case sensitive when you try to establish a shortcut? Mentioned this in a previous post regarding ssf working and SSF not working. But I can not add in SSF as an additional auto insert as the option screen thinks it is the same as ssf.
Tim
Denver, CO / comments
Bart,
Thanks for the reply.
I have already bought my Prompt 3 license so I am waiting anxiously for it's introduction.
Any input on Auto Insert being case sensitive in recognizing the shortcut code...