View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0004294 | SymmetricDS | Bug | public | 2020-02-28 20:57 | 2020-03-04 18:13 |
Reporter | chenson | Assigned To | chenson | ||
Priority | normal | ||||
Status | closed | Resolution | fixed | ||
Product Version | 3.11.5 | ||||
Target Version | 3.11.6 | Fixed in Version | 3.11.6 | ||
Summary | 0004294: Primary key are dropped and created continuously | ||||
Description | This was observed on postgresql. If the order of primary key columns in a Table.java object change, but the columns that make up the primary remain the same, SymmetricDS will detect a primary key change and drop and recreate the primary key with the new order. However, when the Table is read from the database the primary key will be represented by the previous order because the list of pk columns are returned in the order that the columns were create, not in the order that the new primary key represents. This means that the change will be detected again and again. This initial fix is to ignore the order of the primary key columns when detecting primary key changes. The long term fix should be to represent the primary key order correctly in the Table.java class. | ||||
Tags | No tags attached. | ||||
Date Modified | Username | Field | Change |
---|---|---|---|
2020-02-28 20:57 | chenson | New Issue | |
2020-02-28 20:57 | chenson | Status | new => assigned |
2020-02-28 20:57 | chenson | Assigned To | => chenson |
2020-02-28 21:01 | chenson | Status | assigned => confirmed |
2020-03-02 16:13 | elong | Relationship added | related to 0004295 |
2020-03-02 16:13 | elong | Status | confirmed => resolved |
2020-03-02 16:13 | elong | Resolution | open => fixed |
2020-03-02 16:13 | elong | Fixed in Version | => 3.11.6 |
2020-03-04 18:13 | chenson | Status | resolved => closed |