View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000952 | SymmetricDS | Bug | public | 2012-12-13 01:34 | 2014-06-17 00:27 |
| Reporter | chenson | Assigned To | chenson | ||
| Priority | normal | ||||
| Status | closed | Resolution | fixed | ||
| Product Version | 3.1.11 | ||||
| Target Version | 3.6.0 | Fixed in Version | 3.6.0 | ||
| Summary | 0000952: Data can be skipped due to aggressive purge on some platforms | ||||
| Description | MySQL uses the max data_id as the next data_id. If rows 5,6,7,8,9,10 are purged and the next data_id was going to be 11, sym_data_gap would have a gap of 11 to 50,000. The next data_id inserted will be 5 because 5-10 have been purged. data_ids 5-10 will never be routed. Maybe the solution is to never purge the last data_id? | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2012-12-13 01:34 | chenson | New Issue | |
| 2012-12-13 01:46 | chenson | Summary | Some database platforms (mysql) will insert data_ids that are one greater than the last. Bad for combo of purge and data_gap. => Data can be skipped due to aggressive purge on some platforms |
| 2012-12-13 01:46 | chenson | Description Updated | View Revisions |
| 2013-06-08 15:13 | chenson | Target Version | => 3.6.0 |
| 2014-03-03 14:52 | chenson | Assigned To | => gwilmer |
| 2014-03-03 14:52 | chenson | Status | new => assigned |
| 2014-04-18 17:00 | chenson | Assigned To | gwilmer => chenson |
| 2014-05-27 14:52 | chenson | Status | assigned => resolved |
| 2014-05-27 14:52 | chenson | Fixed in Version | => 3.6.0 |
| 2014-05-27 14:52 | chenson | Resolution | open => fixed |
| 2014-05-27 15:00 | Changeset attached | => SymmetricDS trunk r8313 | |
| 2014-06-17 00:27 | chenson | Status | resolved => closed |
| 2015-07-31 01:49 | chenson | Changeset attached | => SymmetricDS master fe2504c6 |