Easily find issues by searching: #<Issue ID>
Example: #1832
Easily find members by searching in: <username>, <first name> and <last name>.
Example: Search smith, will return results smith and adamsmith
| Dev |
|
| QA |
|
| Priority | Low |
| Complexity | Unknown |
| Component | App - SQL Automation |
| Version | 16.0 |
Modified code so that [Introduce Columns] will now take the [Quote Identifier for Column Completion] value into play. the [Introduce Qualified Columns] will also take the [Quote Identifier for Column Completion] value into play, but will not use the [Quote Identifier for Table Completion] value; Instead it will continue to use the qualified table name variable that is representing the table name as the user has it the statement.
We can further modify for qualifying table names in the column area to use the table quote qualifier but this will change behavior so we should file an issue and examine the affects it will have on current users.
Changes made so that the column names will now be correctly qualified when using the [Introduce Columns] & [Introduce Qualified Columns] actions
Changes made so that the column names will now be correctly qualified when using the [Introduce Columns] & [Introduce Qualified Columns] actions
Issue #13344 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| Fixed Build v16.0.5-10, v17.0.0-dev-39 |
| No time estimate |
Modified code so that [Introduce Columns] will now take the [Quote Identifier for Column Completion] value into play. the [Introduce Qualified Columns] will also take the [Quote Identifier for Column Completion] value into play, but will not use the [Quote Identifier for Table Completion] value; Instead it will continue to use the qualified table name variable that is representing the table name as the user has it the statement.
We can further modify for qualifying table names in the column area to use the table quote qualifier but this will change behavior so we should file an issue and examine the affects it will have on current users.