Comments
1 comment
-
Hi Emmanuel,However, there is a glitch I'd like to mention: when I use a fully qualified name, like AdventureWorksDW.dbo.DimProduct where the current database is not AdventureWorksDW, SQLPrompt falls short of providing anything useful. In fact, it just "stays" with the schema of the current database instead of fetching the schema from the qualified database. As a consequence, there are no auto-completion of columns with a statement like Select *{TAB}
Please see this thread
http://www.red-gate.com/MessageBoard/vi ... php?t=3850
Regards,
Tilman
Add comment
Please sign in to leave a comment.
after having tried the previous version of SQL Prompt, I am on for this last beta version. Overall, I have a very good impression w/r to the last one.
One thing I do absolutely love: in a script, when I type USE MyDatabase, SQL Prompt fetches the schema from Mydatabase. Morevover, when the cursor is before the statement USE Database, SQL Prompt will use the schema from the current databse, and only when the cursor is after this statement will SQL Prompt use the schema from MyDatabase. This is absolutely GREAT!!!! It would have saved me quite a lot of time on a six months' project I had last year. Sigh !
However, there is a glitch I'd like to mention: when I use a fully qualified name, like AdventureWorksDW.dbo.DimProduct where the current database is not AdventureWorksDW, SQLPrompt falls short of providing anything useful. In fact, it just "stays" with the schema of the current database instead of fetching the schema from the qualified database. As a consequence, there are no auto-completion of columns with a statement like Select *{TAB}
With kind regards,
Emmanuel