View Issue Details

IDProjectCategoryView StatusLast Update
0000571SymmetricDSBugpublic2012-01-27 16:51
ReporterAssigned Tochenson 
PriorityhighSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version2.2.5 
Target Version2.5.5Fixed in Version2.5.5 
Summary0000571: "Time Zone is not captured/sent to the replicated node for columns that are of type ""Timestamp With Time Zone"""
Description"It appears that the Time zone for the Database itself is used, instead of what is stored for each given row/column. For example we have a table with the following schema: Column | Type | Modifiers --------------+--------------------------+------------------------ oid | integer | not null last_updated | timestamp with time zone | not null default now() nei | integer | not null admin_state | character varying(16) | not null And below are the SymmetricDS defined Functions that capture the last_updated column when changes are made, and they do NOT capture the associated Time Zone faaaa_on_i_nei_admin_state case when new.""last_updated"" is null then '' else '""' || to_char(new.""last_updated"", 'YYYY-MM-DD HH24:MI:SS.MS') || '""' end||','|| faaaa_on_u_nei_admin_state case when new.""last_updated"" is null then '' else '""' || to_char(new.""last_updated"", 'YYYY-MM-DD HH24:MI:SS.MS') || '""' end||','|| faaaa_on_d_nei_admin_state case when old.""last_updated"" is null then '' else '""' || to_char(old.""last_updated"", 'YYYY-MM-DD HH24:MI:SS.MS') || '""' end||','||"
TagsNo tags attached.

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change