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 | Major |
| Complexity | Unknown |
| Component | Tools - Compare - Schema |
| Version | 17.0 |
| fn_cdc_decrement_lsn |
| fn_cdc_increment_lsn |
| fn_cdc_is_bit_set |
| fn_repl_hash_binary |
| GeographyCollectionAggregate |
| GeographyConvexHullAggregate |
| GeographyEnvelopeAggregate |
| GeographyUnionAggregate |
| GeometryCollectionAggregate |
| GeometryConvexHullAggregate |
| GeometryEnvelopeAggregate |
| GeometryUnionAggregate |
| ORMask |
4.Issue is reproducible in V17 only.
5.In V18,if we check DDL of these 13 UDF , null is displayed in schema compare window.
|
|
100 KB
|
|
270 KB
|
11 KB
|
|
75 KB
Stack Trace :
I checked this in V15 and V16, Issue is not reproducible there.
I have updated the attached xls file with list of UDF in all versions.
I checked this in V15 and V16, Issue is not reproducible there.
I have updated the attached xls file with list of UDF in all versions.
@tariq: pls determine exact version when this problem was introduced in v17.
@tariq: pls determine exact version when this problem was introduced in v17.
@Sachin
This issue is reproducible from ADS 17.0.0 alpha-9.
@Sachin
This issue is reproducible from ADS 17.0.0 alpha-9.
@ivan: Take a look at svn#45143. This is the most likely cause of the breakage
<datastudio: 13253> SQL Server -> functions will now also include types AF, FS & FT in tree node, object search, schema generator though extraction and scripting not avaliable
@ivan: Take a look at svn#45143. This is the most likely cause of the breakage
<datastudio: 13253> SQL Server -> functions will now also include types AF, FS & FT in tree node, object search, schema generator though extraction and scripting not avaliable
I've made modifications to the extraction sql so that these objects do not return a null when they have no source associated with them. If they object is unable to function is unable to extract its source, the following string will be set for the objects source info: "// Reverse engineering of object's source DDL is currently not supported." This string has been set in the base object class so that we can use it for all objects types.
When we have objects that we are unable to reverse engineer there DDL this is the message we will show. This means that if two objects are named the same and neither can have there DDL reverse engineered, schema compare will show them as equal to each other even though we do not know if they are equal. issue
NPE will no longer be thrown.
I've made modifications to the extraction sql so that these objects do not return a null when they have no source associated with them. If they object is unable to function is unable to extract its source, the following string will be set for the objects source info: "// Reverse engineering of object's source DDL is currently not supported." This string has been set in the base object class so that we can use it for all objects types.
When we have objects that we are unable to reverse engineer there DDL this is the message we will show. This means that if two objects are named the same and neither can have there DDL reverse engineered, schema compare will show them as equal to each other even though we do not know if they are equal. issue
NPE will no longer be thrown.
Issue #14342 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| Fixed Build v17.0.3-17, v18.0.0-devi-98 |
| No time estimate |
1 issue link |
relates to #14353
Issue #14353Schema Compare -> objects with unsupported DDL extraction always match |
Stack Trace :