Comments
Sort by recent activity
Yes, I am targeting a SQL 2005 instance.
Thanks for your input,
Emmanuel / comments
Yes, I am targeting a SQL 2005 instance.
Thanks for your input,
Emmanuel
This would be my most used snippet:
SELECT TOP 100 * FROM
With kind regards,
Emmanuel
PS: I also use some snippets whose utility would fall because of SQL Prompt, like
SELECT * FROM MyTable WHERE 1 = 0 / comments
This would be my most used snippet:
SELECT TOP 100 * FROM
With kind regards,
Emmanuel
PS: I also use some snippets whose utility would fall because of SQL Prompt, like
SELECT * FROM MyTable WHERE 1...
Hello,
I, for one, do like it: it shows me when the tool is ready, which is most useful when changing to a DB with many objects. And I can still work while it is showing up...
Making it an option could have both of us happy ;-)
With kind regards,
Emmanuel / comments
Hello,
I, for one, do like it: it shows me when the tool is ready, which is most useful when changing to a DB with many objects. And I can still work while it is showing up...
Making it an option c...
Hello,
this is exactly the bug I had on my list for today. Please do not consider rjpaulsen's comment as a mere suggestion: this week I had to do some real work, and SQL Prompt just went across my way each time, and it was very painfull to move in the SQL code with only the keyboard, having to press ESC evrytime to have the list disappear.
Please really consider it as a significant barrier to usability.
With kind regards,
Emmanuel / comments
Hello,
this is exactly the bug I had on my list for today. Please do not consider rjpaulsen's comment as a mere suggestion: this week I had to do some real work, and SQL Prompt just went across my ...
Hello,
This is also my opinion: at least the most important bugs should be corrected in another beta version. Furthermore, I do not think that the most important bugs (in the view of the user, i.e. myself) are the most difficult to fix ...
With kind regards,
Emmanuel / comments
Hello,
This is also my opinion: at least the most important bugs should be corrected in another beta version. Furthermore, I do not think that the most important bugs (in the view of the user, i.e....
Hello,
I do vote for TAB and ENTER as default, and all others as optional. (I think this is also the standard behaviour of intellisense in VS).
With kind regards,
Emmanuel / comments
Hello,
I do vote for TAB and ENTER as default, and all others as optional. (I think this is also the standard behaviour of intellisense in VS).
With kind regards,
Emmanuel
While it would be nice to specify alias on a per table/view basis, this is not yet sufficient: suppose that I want to join a table with itself. Then I would expect the tool to provide me with two different alias names (like myalias and myalias2, for instance...)
Just my 2 cents,
Emmanuel / comments
While it would be nice to specify alias on a per table/view basis, this is not yet sufficient: suppose that I want to join a table with itself. Then I would expect the tool to provide me with two d...
Hello,
for me, there is no need for an option: intellisense should not work inside comments! Indeed, if I want intellisense for code inside comments, I uncomment my comment just for the time while I am writing it, and then I "redo" my comment. While fulfilling my ususal tasks, I expect it would take longer to go in the options and to turn them on/off...
Just my 2cents,
Emmanuel / comments
Hello,
for me, there is no need for an option: intellisense should not work inside comments! Indeed, if I want intellisense for code inside comments, I uncomment my comment just for the time while ...
Hello,
going on with my discovery of the tool, here are a few gotchas I'd like to mention. I am using the database AdventureWorks (in my previous post, it was Northwind).
There is something weird about the default options: the dot shouldn't be a completion character. Or maybe better the tool should recognize the alias, in the following example: if I type
select * from [Person].[Contact] AS c
where c
where c is the alias provided by SQL Prompt, and I type then a dot, the result is:
select * from [Person].[Contact] AS c
where CREATE ACTION .
When I type
select * from [Person].[Contact] AS c left join
I am presented with a list of columns, while I would expect a list of tables/views.
Likewise, if I have a query like the following:
select * from [Person].[Contact] AS c left join Contact AS c2
when I type the keyword ON, I would expect it to appear at the begining of the list. Since this is not the case, I end up with the following result:
select * from [Person].[Contact] AS c left join Contact AS c2 soh.[OnlineOrderFlag] , [Sales].[SalesOrderHeader] AS soh
(For those inetrested, the list presented by the tool begins with:
OnlineOrderFlag, OnOrderQty, ON, ON DEFAULT, etc). My guess is that the list is presented in an alphabetical order wich is case sensitive!
On a completely unrelated note, I want to be able to customize SQL Prompt by adding my own code snippets (like ata for ALTER TABLE ADD). This is not (yet ?) the case...
Another thing that annoys me: if I am typing towards the right end of my screen the candidate lists shows up with a good part of it outside the screen... This is a big NO for me.
Well, that's all for now... / comments
Hello,
going on with my discovery of the tool, here are a few gotchas I'd like to mention. I am using the database AdventureWorks (in my previous post, it was Northwind).
There is something weird a...
Superb!
Thanks a lot for this tip!
Kind regards,
Emmanuel / comments
Superb!
Thanks a lot for this tip!
Kind regards,
Emmanuel