Comments
Sort by recent activity
Hi Emmanuel,
Please see these threads http://www.red-gate.com/MessageBoard/vi ... ight=grant http://www.red-gate.com/MessageBoard/vi ... ight=grant
Regards,
Tilman / comments
Hi Emmanuel,
Please see these threadshttp://www.red-gate.com/MessageBoard/vi ... ight=granthttp://www.red-gate.com/MessageBoard/vi ... ight=grant
Regards,
Tilman
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 / comments
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 f...
Hi,
Thanks for posting. I'm afraid I couldn't reproduce your problem. Any chance you could give me a more detailed example?
Cheers,
Tilman / comments
Hi,
Thanks for posting. I'm afraid I couldn't reproduce your problem. Any chance you could give me a more detailed example?
Cheers,
Tilman
Hi Mike,
The snippets are saved here
%USERPROFILE%\Local Settings\Application Data\Red Gate\SQL Prompt 3\SQL Prompt 3 Snippets.xml
Let us know if you find anything. There is at least one other person who seems to have the same problem.
Regards,
Tilman / comments
Hi Mike,
The snippets are saved here
%USERPROFILE%\Local Settings\Application Data\Red Gate\SQL Prompt 3\SQL Prompt 3 Snippets.xml
Let us know if you find anything. There is at least one other pers...
Hi,
Thank you for reporting this issue. I've added it to our system.
Regards,
Tilman / comments
Hi,
Thank you for reporting this issue. I've added it to our system.
Regards,
Tilman
Hi Travis,
Thanks for the feedback. This is a known issue which fell by the way due to time constraints. We are planning to address this in a future version.
Regards,
Tilman / comments
Hi Travis,
Thanks for the feedback. This is a known issue which fell by the way due to time constraints. We are planning to address this in a future version.
Regards,
Tilman
Hi,
1) from memory, you used to be able to order the candidate list the same was as the columns in the table were ordered, or alphabetically...would be nice to have that option again
I'm afraid currently we can only do alphabetical due to the data structure we use to store the candidates.
2) would be good if it supported queries involving more than one database
Please see this thread http://www.red-gate.com/MessageBoard/vi ... php?t=3850
Regards,
Tilman / comments
Hi,
1) from memory, you used to be able to order the candidate list the same was as the columns in the table were ordered, or alphabetically...would be nice to have that option again
I'm afraid c...
Hi,
I'd like to see the joins go BOTH ways if possible. I actually prefer doing <table I'm joining to>.col = <table I'm joining from>.col. A small semantic difference, but just the way I like to write my SQL.
This has already been suggested, and it's on our list, but I don't think it will make it into v3.
Now, a version that doesn't work... did you know that the ON clause can go in one of two places?
SELECT *
FROM [HumanResources].[EmployeeAddress] ea
JOIN [HumanResources].[Employee] e
JOIN [HumanResources].[EmployeeDepartmentHistory] edh ON e.[EmployeeID] = edh.[EmployeeID]
ON --***
Hit space before the *** comment and you'll get a column list rather than JOIN candidates. The ONs here are nested in the same order as the JOINs, so you should get a list of candidates for the JOIN between "e" and "ea". (Note, I absolutely *hate* this syntax, but I see it from time to time so I suppose it should be supported)
I actually didn't know this. Thanks for pointing it out. I've added an issue to our system.
Now, another weird thing... What if I accidentally leave the ON below the JOINs?
SELECT *
FROM [HumanResources].[EmployeeAddress] ea
JOIN [HumanResources].[Employee] e ON --***
JOIN [HumanResources].[EmployeeDepartmentHistory] edh ON e.[EmployeeID] = edh.[EmployeeID]
ON
Again, hit space before the *** comment and it's broken... Until I do something like:
SELECT *
FROM [HumanResources].[EmployeeAddress] ea
JOIN [HumanResources].[Employee] e ON --***
JOIN [HumanResources].[EmployeeDepartmentHistory] edh ON e.[EmployeeID] = edh.[EmployeeID]
ON x
This is kind of expected behaviour. Our parser doesn't work very well with invalid SQL (which is kind of ironic, i know, but hey...), so as a rule of thumb, the more valid the SQL the better Prompt will work.
Regards,
Tilman / comments
Hi,
I'd like to see the joins go BOTH ways if possible. I actually prefer doing <table I'm joining to>.col = <table I'm joining from>.col. A small semantic difference, but just the way I like to w...
Hi,
Hi, I just started using Sql Prompt 3 after finding the announcement, I've been using Sql Prompt for at least 6 months now and I really love it. Sql Prompt 2 had support for the ON clause where I could type INNER JOIN ON and it would drop down a set of matching IDs which was very useful... any idea if this will integrate into sql prompt 3?
This should be working. We always suggest join conditions based on foreign keys. There are also options to get join conditions based on column name and column type. Could you give me a specific example where this isn't working?
SELECT A.Field1, A.Field2, B.Field1
From TableA AS A INNER JOIN TableB AS B ON A.FieldPK = B.FieldPK
When I type B. SqlPrompt2 would list me a set of fields related only to Table B if I did A. I would get a list of only fields in tableA, Sql Prompt3 doesn't seem to do that, it seems to give me all the fields wich is not useful at all.
Again, I can't reproduce this.
Could you tell me a bit about your set up? I.e. what editor are you using, what version is it? SQL Server version and language? What's your OS/language?
Regards,
Tilman / comments
Hi,
Hi, I just started using Sql Prompt 3 after finding the announcement, I've been using Sql Prompt for at least 6 months now and I really love it. Sql Prompt 2 had support for the ON clause whe...
Hi,
I'm afraid this is by design. We do not detect at the moment when the schema changes.
Regards,
Tilman / comments
Hi,
I'm afraid this is by design. We do not detect at the moment when the schema changes.
Regards,
Tilman