View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0003461 | SymmetricDS | Bug | public | 2018-02-28 14:21 | 2022-09-21 21:07 |
Reporter | rayp | Assigned To | elong | ||
Priority | normal | ||||
Status | closed | Resolution | fixed | ||
Product Version | 3.9.4 | ||||
Target Version | 3.11.10 | Fixed in Version | 3.11.10 | ||
Summary | 0003461: mysql bulk loader doesn't work with binary() columns, tries to insert in wrong column. | ||||
Description | During an initial load of a table that has one or more binary() column, my logs were spammed with errors about wrong data types when I know my input data was clean. I realized that it was trying to insert data in the column next to the proper one. After a lengthy discussion on the forum, someone (Lukas) suggested that it may be the bulk loader. Disabling the bulk loader fixed the problem. I had 2 tables with binary columns and both gave tons of errors when trying to do initial loads. Here's a link to the forum discussion, specifically the problem code: https://sourceforge.net/p/symmetricds/discussion/739236/thread/52ebedea/#65e0 | ||||
Steps To Reproduce | Set up a sync using mysql bulk loader and load some tables with binary() data types. | ||||
Additional Information | I've had this problem with every version of SDS I've used, 3.9.2 - 3.9.4. | ||||
Tags | bulk, dialect: mysql/mariadb | ||||
related to | 0004433 | closed | JJ_Starrett | MySql Bulk loader fails on Hex encoded BLOBs and CLOBs |
Date Modified | Username | Field | Change |
---|---|---|---|
2018-02-28 14:21 | rayp | New Issue | |
2019-04-24 17:35 | elong | Tag Attached: bulk | |
2019-04-24 17:35 | elong | Tag Attached: dialect: mysql/mariadb | |
2022-08-05 14:47 | elong | Relationship added | related to 0004433 |
2022-08-05 14:48 | elong | Assigned To | => elong |
2022-08-05 14:48 | elong | Status | new => resolved |
2022-08-05 14:48 | elong | Resolution | open => fixed |
2022-08-05 14:48 | elong | Fixed in Version | => 3.11.10 |
2022-09-21 21:07 | elong | Status | resolved => closed |