View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003673 | SymmetricDS | Bug | public | 2018-08-15 12:49 | 2018-08-20 14:52 |
| Reporter | elong | Assigned To | elong | ||
| Priority | normal | ||||
| Status | closed | Resolution | fixed | ||
| Product Version | 3.9.0 | ||||
| Target Version | 3.9.12 | Fixed in Version | 3.9.12 | ||
| Summary | 0003673: Auto resolve foreign key can fail when primary keys are not first in table definition | ||||
| Description | The auto resolution of missing foreign keys can fail when the table definition has primary keys that are not listed as the first columns. SymmetricDS is internally re-ordering columns so the primary keys are first when issuing inserts. The list of column values is passed to the routine to resolve FKs and it uses the table definition from the cache without re-ordering it, so the column names don't match up with column values. create table example (name varchar, id integer primary key); | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2018-08-15 12:49 | elong | New Issue | |
| 2018-08-15 12:49 | elong | Status | new => assigned |
| 2018-08-15 12:49 | elong | Assigned To | => elong |
| 2018-08-15 12:51 | elong | Issue cloned: 0003674 | |
| 2018-08-15 12:51 | elong | Relationship added | related to 0003674 |
| 2018-08-15 12:59 | elong | Status | assigned => resolved |
| 2018-08-15 12:59 | elong | Resolution | open => fixed |
| 2018-08-15 12:59 | elong | Fixed in Version | => 3.9.12 |
| 2018-08-15 13:00 | admin | Changeset attached | => SymmetricDS 3.9 df9356c8 |
| 2018-08-20 14:52 | mmichalek | Status | resolved => closed |