View Issue Details

Related ChangesetsJump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0004134SymmetricDSBugpublic2019-10-30 13:082022-08-30 13:04
Reporternrichardson Assigned Toemiller  
Prioritynormal 
Status closedResolutionfixed 
Target Version3.14.1Fixed in Version3.14.1 
Summary0004134: DB Compare does not handle Oracle Timestamp with LOCAL time zone columns properly
DescriptionWhen issuing a select with to_char("column_name", 'YYYY-MM-DD HH24:MI:SS.FF TZH:TZM') on an Oracle column defined as TIMESTAMP(n) WITH LOCAL TIME ZONE it will fail. Oracle only allows the TZD or TZR options. These options are valid with a regular WITH TIME ZONE data type just not LOCAL.
For LOCAL TIME ZONE fields we should use something like to_char("column_name", 'YYYY-MM-DD HH24:MI:SS.FF9')
Steps To ReproduceCreate an Oracle table with a TIMESTAMP(6) WITH LOCAL TIME ZONE column and run the db compare.
Tagsdbcompare

Activities

There are no notes attached to this issue.

Related Changesets

SymmetricDS: 3.14 58c827f1

2022-08-08 16:04:28

evan-miller-jumpmind

Details Diff 		0004134: Fixed how dbcompare handles Oracle timestamp with local time zone columns Affected Issues
0004134
mod - symmetric-db/src/main/java/org/jumpmind/db/platform/oracle/OracleDmlStatement.java Diff File

Issue History

Date Modified Username Field Change
2019-10-30 13:08 nrichardson New Issue
2019-10-30 14:34 elong Tag Attached: dbcompare
2022-08-08 16:04 emiller Assigned To => emiller
2022-08-08 16:04 emiller Status new => resolved
2022-08-08 16:04 emiller Resolution open => fixed
2022-08-08 16:04 emiller Fixed in Version => 3.14.1
2022-08-08 17:00 Changeset attached => SymmetricDS 3.14 58c827f1
2022-08-30 13:04 admin Status resolved => closed