View Issue Details

IDProjectCategoryView StatusLast Update
0003673SymmetricDSBugpublic2018-08-20 10:52
ReporterelongAssigned Toelong 
Prioritynormal 
Status closedResolutionfixed 
Product Version3.9.0 
Target Version3.9.12Fixed in Version3.9.12 
Summary0003673: Auto resolve foreign key can fail when primary keys are not first in table definition
DescriptionThe 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);

Relationships

related to 0003674 closedelong Auto resolve foreign key can fail when primary keys are not first in table definition 

Activities

There are no notes attached to this issue.

Related Changesets

SymmetricDS: 3.9 df9356c8

2018-08-15 08:58:56

admin

Details Diff
0003673: Auto resolve foreign key can fail when primary keys are not
first in table definition

0003673
mod - symmetric-core/src/main/java/org/jumpmind/symmetric/service/impl/DataService.java Diff File

Issue History

Date Modified Username Field Change
2018-08-15 08:49 elong New Issue
2018-08-15 08:49 elong Status new => assigned
2018-08-15 08:49 elong Assigned To => elong
2018-08-15 08:51 elong Issue cloned: 0003674
2018-08-15 08:51 elong Relationship added related to 0003674
2018-08-15 08:59 elong Status assigned => resolved
2018-08-15 08:59 elong Resolution open => fixed
2018-08-15 08:59 elong Fixed in Version => 3.9.12
2018-08-15 09:00 admin Changeset attached => SymmetricDS 3.9 df9356c8
2018-08-20 10:52 mmichalek Status resolved => closed