View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0005417 | SymmetricDS | Bug | public | 2022-08-22 18:01 | 2022-08-30 13:04 |
Reporter | josh-a-hicks | Assigned To | josh-a-hicks | ||
Priority | normal | ||||
Status | closed | Resolution | fixed | ||
Product Version | 3.14.0 | ||||
Target Version | 3.14.1 | Fixed in Version | 3.14.1 | ||
Summary | 0005417: Fix NPE for conflict detection when table does not have a PK and all columns used including those with null values | ||||
Description | Conflict detection will use all columns if the table does not have a primary key. This can cause a null pointer exception while checking timestamps if any of the values have a null value. StackTraceKey.init [NullPointerException:2347119521] java.lang.NullPointerException at org.jumpmind.symmetric.io.data.writer.DefaultDatabaseWriterConflictResolver.modifyTimestampsForPrecision(DefaultDatabaseWriterConflictResolver.java:211) | ||||
Tags | No tags attached. | ||||
SymmetricDS: 3.14 0e9fb934 2022-08-22 18:01:32 joshahicks Details Diff |
0005417: Fix NPE for conflict detection when table does not have a PK and all columns used including those with null values |
Affected Issues 0005417 |
|
mod - symmetric-io/src/main/java/org/jumpmind/symmetric/io/data/writer/DefaultDatabaseWriterConflictResolver.java | Diff File |
Date Modified | Username | Field | Change |
---|---|---|---|
2022-08-22 18:01 | josh-a-hicks | New Issue | |
2022-08-22 18:01 | josh-a-hicks | Status | new => assigned |
2022-08-22 18:01 | josh-a-hicks | Assigned To | => josh-a-hicks |
2022-08-24 17:38 | josh-a-hicks | Status | assigned => resolved |
2022-08-24 17:38 | josh-a-hicks | Resolution | open => fixed |
2022-08-24 17:38 | josh-a-hicks | Fixed in Version | => 3.14.1 |
2022-08-29 19:00 | Changeset attached | => SymmetricDS 3.14 0e9fb934 | |
2022-08-30 13:04 | admin | Status | resolved => closed |