6 results found
-
When using the "Qualify Object Names" feature, show a drop-down when multiple possibilities exist
e.g.
declare @1 table (a int, b int)
declare @2 table (a INT, b int)SELECT a, b FROM
@1 a
CROSS JOIN @2 bHere there are 2 possibilities for columns a and b, however SQL prompt only suggests the second one. Both should be shown and the user given the chance to choose.
SQL Prompt does not recognize the ambiguity nor alert the user to it (although Microsoft Intellisense does flag the ambiguity). This can result in the user selecting the wrong alias (since only one is presented, apparently the last one found) which can result in hard-to-debug…
1 vote -
remove square brackets from keywords like MATCH clause in a graph table join
when formatting SQL, do not automatically add brackets to the MATCH clause when querying graph tables
1 vote -
Add Per Database table/view alias mapping dictionary for use with Qualify object names
It would be nice to have a setting per database in SQL Prompt that would allow us to set an alias to tablename mapping and these settings can be shared / stored in source control for other developers.
When we run the qualify object name operation it could look at this dictionary and automatically inject an new alias for an old alias or table/view with no alias.
This allows us to have consistently alias'd tables across all sql objects in source control.
2 votes -
Add Feature to Qualify Object Name on files in a folder / directory / sql database
As SQL Prompt user, I want to be able to perform a qualify object names operation on a directory of views, tables, sprocs, etc.
Currently, one must open a sql file in SSMS first then run the qualify object names operation on each file. This is extremely time consuming. We are trying to improve our code quality and readabily by following best practices.
1 vote -
Automatically alias tables and columns in existing scripts
Please could you add a feature that parses a query that has already been written, adds aliases for tables that don't already have them and update columns to use those aliases.
This is because I often get pieces of code which are partially aliased and I have to go through updating the missing ones. Thanks.
15 votes -
Option to include the schema when generating an alias.
I have tables that repeat in different schemas, for example Supplier.Location and Customer.Location. I'd really like auto-alias to include the schema when generating the alias. Supplier.Location should be SL and Customer.Location should be CL. Instead I end up with L and L2, which is not as clear.
Ideally, I'd prefer the schema characters to be lowercase and the table to be uppercase. Using sL and cL would make my query even more readable.
13 votes
- Don't see your idea?