View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001542 | Database Workbench v5 | Diagramming | public | 2017-10-24 17:26 | 2018-03-06 09:09 |
| Reporter | Stephen Lappin | Assigned To | Martijn Tonies | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Platform | Windows 7 64 bit | ||||
| Product Version | 5.3.2 | ||||
| Fixed in Version | 5.4.2 | ||||
| Summary | 0001542: Lose MySQL ON UPDATE TIMESTAMP setting when saving and re-loading diagram | ||||
| Description | On a MySQL PDM, for a Timestamp field: - where ON_UPDATE_TIMESTAMP is checked, and the model saved, this is lost when the model is reopened (looks like setting is not saved) | ||||
| Steps To Reproduce | Define table with Timestamp field - set the default value to CURRENT_TIMESTAMP - check ON_UPDATE_TIMESTAMP - review DDL - it is as expected. - save PDM - close diagram tool - reopen diagram tool and PDM model - ON_UPDATE_TIMESTAMP is no longer checked, and DDL does not include ON_UPDATE_TIMESTAMP clause | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2017-10-24 17:26 | Stephen Lappin | New Issue | |
| 2018-02-14 15:46 | Martijn Tonies | Assigned To | => Martijn Tonies |
| 2018-02-14 15:46 | Martijn Tonies | Status | new => assigned |
| 2018-02-14 15:56 | Martijn Tonies | Status | assigned => resolved |
| 2018-02-14 15:56 | Martijn Tonies | Fixed in Version | => 5.4.2 |
| 2018-02-14 15:56 | Martijn Tonies | Resolution | open => fixed |
| 2018-02-19 12:44 | Martijn Tonies | Summary | Lose ON UPDATE TIMESTAMP setting => Lose MySQL ON UPDATE TIMESTAMP setting when saving and re-loading diagram |
| 2018-03-06 09:09 | Martijn Tonies | Status | resolved => closed |
