You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using a column of timestamp without time zone type and the date/time values have higher precision than seconds, things do not work correctly:
dump of table data will create a diff with values truncated to whole seconds (see allColumnNames() in postgresdriver.cpp)
if such dump is applied to a different schema and then the two schemas are compared, geodiff will emit update entries (because the original value and new value are not the same), but the entries will not contain any actual changes (only primary key column is listed in the entry) - I would consider such diff invalid
Ideally we would want to preserve full original values if possible. And if we need to modify how date/time values are stored in diffs, we should verify the change is backwards compatible.
The text was updated successfully, but these errors were encountered:
When using a column of
timestamp without time zone
type and the date/time values have higher precision than seconds, things do not work correctly:allColumnNames()
in postgresdriver.cpp)update
entries (because the original value and new value are not the same), but the entries will not contain any actual changes (only primary key column is listed in the entry) - I would consider such diff invalidIdeally we would want to preserve full original values if possible. And if we need to modify how date/time values are stored in diffs, we should verify the change is backwards compatible.
The text was updated successfully, but these errors were encountered: