View Issue Details

IDProjectCategoryView StatusLast Update
0004245SymmetricDSBugpublic2020-01-23 20:41
Reporterpmarzullo Assigned Topmarzullo  
Status closedResolutionfixed 
Product Version3.10.8 
Target Version3.10.9Fixed in Version3.10.9 
Summary0004245: Conflict Resolution: Problem with timestamp with time zones as the USE_TIMESTAMP column
DescriptionWhen the USE_TIMESTAMP type of conflict resolution is configured, and the specified column is a Timestamp with time zone type of column, we have problems parsing that type of column, and the conflict resolution does not get resolved.
Steps To Reproduce1. Configure conflict resolution with a USE_TIMESTAMP type, and specify the timestamp column to use that is a timestamp with time zone type.
2. Cause a conflict, where the target timestamp with time zone column has a value greater than the source column.
3. The source values will still be written to the target.
Additional InformationOracle and Postgres have timestamp with time zone types.
Tagsconflict manager


There are no notes attached to this issue.

Related Changesets

SymmetricDS: 3.10 469c62bc

2020-01-17 13:10:28

Philip Marzullo

Details Diff
0004245: Conflict Resolution: Problem with timestamp with time zones as
the USE_TIMESTAMP column
Affected Issues
mod - symmetric-db/src/main/java/org/jumpmind/db/sql/ Diff File
mod - symmetric-io/src/main/java/org/jumpmind/symmetric/io/data/writer/ Diff File
mod - symmetric-util/src/main/java/org/jumpmind/util/ Diff File

Issue History

Date Modified Username Field Change
2020-01-17 18:07 pmarzullo New Issue
2020-01-17 18:07 pmarzullo Status new => assigned
2020-01-17 18:07 pmarzullo Assigned To => pmarzullo
2020-01-17 18:07 pmarzullo Tag Attached: conflict manager
2020-01-17 18:10 pmarzullo Status assigned => resolved
2020-01-17 18:10 pmarzullo Resolution open => fixed
2020-01-17 18:10 pmarzullo Fixed in Version => 3.10.9
2020-01-17 19:00 Changeset attached => SymmetricDS 3.10 469c62bc
2020-01-23 20:41 admin Status resolved => closed