View Issue Details

IDProjectCategoryView StatusLast Update
0003674SymmetricDSBugpublic2018-11-28 18:24
Reporterelong Assigned Toelong  
Prioritynormal 
Status closedResolutionfixed 
Product Version3.8.0 
Target Version3.8.41Fixed in Version3.8.41 
Summary0003674: 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);
TagsNo tags attached.

Relationships

related to 0003673 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.8 a4657868

2018-08-15 08:57:52

admin

Details Diff
0003674: Auto resolve foreign key can fail when primary keys are not
first in table definition
Affected Issues
0003674
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 12:51 elong New Issue
2018-08-15 12:51 elong Status new => assigned
2018-08-15 12:51 elong Assigned To => elong
2018-08-15 12:51 elong Issue generated from: 0003673
2018-08-15 12:51 elong Relationship added related to 0003673
2018-08-15 12:58 elong Status assigned => resolved
2018-08-15 12:58 elong Resolution open => fixed
2018-08-15 12:58 elong Fixed in Version => 3.8.41
2018-08-15 13:00 admin Changeset attached => SymmetricDS 3.8 a4657868
2018-11-28 18:24 mmichalek Status resolved => closed