View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004164 | SymmetricDS Pro | Bug | public | 2019-11-24 21:47 | 2019-12-02 20:10 |
| Reporter | zeljko.katic@procosafe.no | Assigned To | elong | ||
| Priority | normal | ||||
| Status | closed | Resolution | fixed | ||
| Product Version | 3.11.0 | ||||
| Target Version | 3.11.1 | Fixed in Version | 3.11.1 | ||
| Summary | 0004164: BatchUpdateException: Duplicate entry '24-378' for key 'PRIMARY' | ||||
| Description | When joining a client(with MSSQL) to SymmetricDS server(withMysql) Duplicate entry appears. It happens even when the client db is truncated. Tried to fix the problem with the regular MySQL fixes on the Duplicate Entry matter but failing. Also after clearing the log the error just reappears and cannot find the duplicated entry in the server db. This problem was not appearing in version 3.10.4 | ||||
| Steps To Reproduce | Add a local node to the server. | ||||
| Tags | No tags attached. | ||||
|
|
|
|
|
This looks like the same as issue 0004162 . We'll try to do a release soon this week as it's easy to get with more than 2 node groups. |
|
|
Yes it does. Because I have not noticed this in 3.10.4. Thank you |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2019-11-24 21:47 | zeljko.katic@procosafe.no | New Issue | |
| 2019-11-24 21:47 | zeljko.katic@procosafe.no | File Added: logs.zip | |
| 2019-11-24 21:54 | elong | Relationship added | duplicate of 0004162 |
| 2019-11-24 21:56 | elong | Note Added: 0001654 | |
| 2019-11-24 22:13 | zeljko.katic@procosafe.no | Note Added: 0001655 | |
| 2019-11-25 14:07 | elong | Assigned To | => elong |
| 2019-11-25 14:07 | elong | Status | new => resolved |
| 2019-11-25 14:07 | elong | Resolution | open => fixed |
| 2019-11-25 14:07 | elong | Fixed in Version | => 3.11.1 |
| 2019-11-25 14:07 | elong | Target Version | => 3.11.1 |
| 2019-11-25 14:07 | elong | Description Updated | View Revisions |
| 2019-12-02 20:10 | admin | Status | resolved => closed |