View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004666 | SymmetricDS | Bug | public | 2020-11-26 02:23 | 2022-08-02 20:12 |
| Reporter | scott_burgess | Assigned To | |||
| Priority | normal | ||||
| Status | new | Resolution | open | ||
| Product Version | 3.12.5 | ||||
| Summary | 0004666: dbcompare comparison SQL isn't right for tables with multi-col primary keys | ||||
| Description | In 3.12.0, dbcompare worked correctly when constructing the comparison SQL: (Source is Oracle, Target is Azure SQL) Source comparison SQL: select "EQUIPMENT", "VEHICLE", "SEQUENCE" from "EQUIPMENT" t where 1=1 ORDER BY "EQUIPMENT","VEHICLE" Target comparison SQL: select "equipment", "vehicle", "sequence" from "equipment" t where 1=1 ORDER BY "equipment","vehicle" However after upgrading to 3.12.5, the columns selected are in a different order and order by columns are as well, causing most rows to fail. Source comparison SQL: select "VEHICLE", "EQUIPMENT", "SEQUENCE" from "EQUIPMENT" t where 1=1 ORDER BY "EQUIPMENT","VEHICLE" Target comparison SQL: select "equipment", "vehicle", "sequence" from "equipment" t where 1=1 ORDER BY "vehicle","equipment" Running dbcompare from 3.12.0 again shows the expected results. | ||||
| Steps To Reproduce | Run dbcompare on a database table that has multi-column primary keys. Compare comparison SQL between the two. | ||||
| Tags | dbcompare | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2020-11-26 02:23 | scott_burgess | New Issue | |
| 2020-12-02 18:57 | elong | Note Added: 0001866 | |
| 2022-08-02 20:12 | elong | Tag Attached: dbcompare |