Easily find issues by searching: #<Issue ID>
Example: #1832
When scripting constraints for db2 i Series, should the constraint name have <schema>.<name> format?
| Field | Old Value | New Value |
|---|---|---|
| Version | 16.0 | 15.0 |
| Field | Old Value | New Value |
|---|---|---|
| Description | When scripting constraints for db2 i Series, should the constraint name have <schema>.<name> format? |
| Field | Old Value | New Value |
|---|---|---|
| Status | New | In Progress |
| Field | Old Value | New Value |
|---|---|---|
| Fixed Build | v16.0.0-rc-4 | |
| Resolution | Fixed | |
| Resolved Date | Mar 10, 2015 5:45 PM | |
| Status | In Progress | Resolved |
As of version 5.2 the constraint name will be qualified with its schema. will back port changes to version 15.
| Field | Old Value | New Value |
|---|---|---|
| Status | Resolved | Closed |
Verified in ADS v15.0.14-19 for Script Create Table. There is another issue which I have logged #13138 in which individual constraints are not scripted correctly
Verified in ADS v15.0.14-19 for Script Create Table. There is another issue which I have logged #13138 in which individual constraints are not scripted correctly
Issue #13114 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| Fixed Build v16.0.0-rc-4 |
| No time estimate |
1 issue link |
relates to #13138
Issue #13138DB2 iSeries -> Primary key constraint -> Scripting: Schema is not appended for Create/Drop |
As of version 5.2 the constraint name will be qualified with its schema. will back port changes to version 15.