View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000401 | Database Workbench v4 | Compare & Migration | public | 2012-07-15 22:02 | 2014-01-27 13:09 |
| Reporter | Jeroen Pluimers | Assigned To | Martijn Tonies | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Fixed in Version | 4.4.4 | ||||
| Summary | 0000401: SQL Server compare, "nocheck" is not in script after compare | ||||
| Description | This diff does end up in the comparison tree, but not in the script: ALTER TABLE dbo.ALGT_Applicatie WITH NOCHECK ADD CONSTRAINT FK_ALGT_Applicatie_ALGT_AppServer FOREIGN KEY (AppServer) REFERENCES dbo.ALGT_AppServer (AppServerID) ON DELETE NO ACTION ON UPDATE NO ACTION GO The diff is subtle: Source database has the constraint as CHECK, destination as NOCHECK. | ||||
| Tags | No tags attached. | ||||
| DBMS & Version | |||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2012-07-15 22:02 | Jeroen Pluimers | New Issue | |
| 2012-07-16 10:12 | Martijn Tonies | Status | new => acknowledged |
| 2013-12-18 11:50 | Martijn Tonies | Assigned To | => Martijn Tonies |
| 2013-12-18 11:50 | Martijn Tonies | Status | acknowledged => assigned |
| 2013-12-18 11:50 | Martijn Tonies | Summary | SQL Server database compare: not all differences end up in the script => SQL Server compare, "nocheck" is not in script after compare |
| 2013-12-18 16:12 | Martijn Tonies | Status | assigned => resolved |
| 2013-12-18 16:12 | Martijn Tonies | Fixed in Version | => 4.4.4 |
| 2013-12-18 16:12 | Martijn Tonies | Resolution | open => fixed |
| 2014-01-13 15:09 | Martijn Tonies | View Status | private => public |
| 2014-01-27 13:09 | Martijn Tonies | Status | resolved => closed |
