View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0000262 | SymmetricDS | Bug | public | 2010-01-06 17:05 | 2022-08-11 13:26 |
Reporter | Assigned To | chenson | |||
Priority | high | ||||
Status | closed | Resolution | fixed | ||
Product Version | 2.0.5 | ||||
Target Version | 2.1.0 | Fixed in Version | 2.1.0 | ||
Summary | 0000262: Blob/Clob not updating for MySQL and Derby | ||||
Description | For dialects that have to select LOB data back out of the original tables, the old and new data was always the same. This meant that when the data loader is building its update statement, it always leaves out the lob column. The solution is to always return null for the old lob data (why go back to the original table?) and change the tabletemplate to always update lob columns for databases that have this issue. | ||||
Tags | No tags attached. | ||||
related to | 0002597 | acknowledged | Bug in update trigger for table with nvarchar(MAX) field (MS SQL) |
Date Modified | Username | Field | Change |
---|---|---|---|
2022-08-11 13:26 | emiller | Relationship added | related to 0002597 |