View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006572 | SymmetricDS | Bug | public | 2024-08-30 17:28 | 2024-08-30 18:00 |
| Reporter | elong | Assigned To | elong | ||
| Priority | normal | ||||
| Status | closed | Resolution | fixed | ||
| Product Version | 3.9.16 | ||||
| Target Version | 3.15.9 | Fixed in Version | 3.15.9 | ||
| Summary | 0006572: SQL Server updates create duplicate rows with datetime2 in primary key | ||||
| Description | On SQL-Server, when using datetime2(7) in the primary key, and using db.treat.date.time.as.varchar.enabled=true parameter, updates will cause a duplicate row to be inserted. This is happening because the string of timestamp is cast to a datetime2(6), so only the microseconds are used instead of the nanoseconds. | ||||
| Tags | dialect: sql-server | ||||
| related to | 0003837 | resolved | josh-a-hicks | MSSQL Support for datetime2 values that are before January 1, 1753 |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-08-30 17:28 | elong | New Issue | |
| 2024-08-30 17:28 | elong | Status | new => assigned |
| 2024-08-30 17:28 | elong | Assigned To | => elong |
| 2024-08-30 17:28 | elong | Tag Attached: dialect: sql-server | |
| 2024-08-30 17:30 | elong | Relationship added | related to 0003837 |
| 2024-08-30 17:32 | elong | Status | assigned => resolved |
| 2024-08-30 17:32 | elong | Resolution | open => fixed |
| 2024-08-30 17:32 | elong | Fixed in Version | => 3.15.9 |
| 2024-08-30 18:00 | admin | Changeset attached | => SymmetricDS 3.15 08d18303 |
| 2024-10-01 19:48 | admin | Status | resolved => closed |