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 - Visual Editing |
| Version | 16.0 |
SQL Server Create Object, the schema defaults to first item on the list, instead of dbo
If I create a new Table in SQL Server 2014 using ADS 16.0 it will set the default schema to the first item on the list. But it should set it to "dbo". If you use ADS 12.0 you can see that it correctly sets the schema to "dbo". This is a bug.
Code was basically looking what schema the node that activated the GUI popup was using and if there was one, it would use that one, if there wasn't a schema associated to the node, no schema would get set. This would cause the first item in the list to be selected.
Made changes so that if there is no node schema it will attempt to used the current default schema from the connection. Tariq, lets discuss if this is not what we are looking for the GUI to do.
Verified in ADS v16.0.3-12.
@Ivan: The behavior is as expected and works. Can you confirm Defaults, Rules and Data Type as well ? See attached pics - they default to first item in schema list...
Verified in ADS v16.0.3-12.
@Ivan: The behavior is as expected and works. Can you confirm Defaults, Rules and Data Type as well ? See attached pics - they default to first item in schema list...
I've made some changes to handle defaults rules and data types.
I've made some changes to handle defaults rules and data types.
Datatypes, Defaults, Rules also fixed in ADS v16.0.3-15
Datatypes, Defaults, Rules also fixed in ADS v16.0.3-15
Issue #13215 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| Fixed Build v16.0.3-12,v16.0.3-15 |
| No time estimate |
Code was basically looking what schema the node that activated the GUI popup was using and if there was one, it would use that one, if there wasn't a schema associated to the node, no schema would get set. This would cause the first item in the list to be selected.
Made changes so that if there is no node schema it will attempt to used the current default schema from the connection. Tariq, lets discuss if this is not what we are looking for the GUI to do.