View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003545 | SymmetricDS | Bug | public | 2018-05-04 08:54 | 2018-10-17 09:22 |
| Reporter | woehrl01 | Assigned To | |||
| Priority | normal | ||||
| Status | confirmed | Resolution | open | ||
| Product Version | 3.9.6 | ||||
| Target Version | 3.10.0 | Fixed in Version | |||
| Summary | 0003545: Mapped default values lead to always detecting a model change | ||||
| Description | If you have a default value which gets mapped to a different value on a different dialect you always get a model change detection. | ||||
|
|
Can you perhaps provide an example that would allow us to reproduce this issue? For example, source database platform, target database platform, and table definitions. |
|
|
I commented about a reproduction here: https://github.com/JumpMind/symmetric-ds/pull/80 You can simply check this if you have Oracle Database with SYSTIMESTAMP or SYSDATE default on the source and a Sqlite Database on the client. e.g: create table employee_history ( employee_id number(6) not null, hire_date date default sysdate ) |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2018-05-04 08:54 | woehrl01 | New Issue | |
| 2018-10-10 14:12 | hanes | Status | new => feedback |
| 2018-10-10 14:12 | hanes | Note Added: 0001267 | |
| 2018-10-11 04:38 | woehrl01 | Note Added: 0001270 | |
| 2018-10-11 04:38 | woehrl01 | Status | feedback => new |
| 2018-10-17 09:22 | hanes | Status | new => confirmed |
| 2018-10-17 09:22 | hanes | Target Version | => 3.10.0 |