View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006193 | SymmetricDS | Bug | public | 2024-01-15 18:01 | 2024-01-15 18:14 |
| Reporter | pmarzullo | Assigned To | pmarzullo | ||
| Priority | normal | ||||
| Status | closed | Resolution | fixed | ||
| Product Version | 3.15.2 | ||||
| Target Version | 3.15.3 | Fixed in Version | 3.15.3 | ||
| Summary | 0006193: Adjusting unique indexes to non-unique when columns can be null should be able to be turned off by parameter | ||||
| Description | The functionality to change unique indexes to non-unique indexes, when one of the columns in the index can be null and the database does not allow more than one null value in the unique index for a column, needs to be able to be turned off by parameter if the customer does not want this behavior. Also, when the functionality is executed, the platform specific index information needs to be added to the non-unique index (in the case of SQL Server, the index filter and the index compression). | ||||
| Additional Information | The new parameter is: create.index.convert.unique.to.nonunique.when.columns.not.required and defaults to true. | ||||
| Tags | ddl/schema | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-01-15 18:01 | pmarzullo | New Issue | |
| 2024-01-15 18:01 | pmarzullo | Status | new => assigned |
| 2024-01-15 18:01 | pmarzullo | Assigned To | => pmarzullo |
| 2024-01-15 18:01 | pmarzullo | Tag Attached: ddl/schema | |
| 2024-01-15 18:01 | pmarzullo | Relationship added | related to 0005782 |
| 2024-01-15 18:01 | pmarzullo | Relationship added | related to 0006192 |
| 2024-01-15 18:14 | pmarzullo | Status | assigned => resolved |
| 2024-01-15 18:14 | pmarzullo | Resolution | open => fixed |
| 2024-01-15 18:14 | pmarzullo | Fixed in Version | => 3.15.3 |
| 2024-01-15 18:14 | pmarzullo | Note Added: 0002405 | |
| 2024-02-05 18:58 | admin | Status | resolved => closed |