View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0005806 | SymmetricDS Pro | Bug | public | 2023-04-21 19:56 | 2023-04-21 20:09 |
Reporter | pmarzullo | Assigned To | pmarzullo | ||
Priority | normal | ||||
Status | closed | Resolution | fixed | ||
Product Version | 3.14.6 | ||||
Target Version | 3.14.7 | Fixed in Version | 3.14.7 | ||
Summary | 0005806: Cloud bulk load fails when source and target table columns do not match | ||||
Description | When the number of columns or the order of columns are not the same between the source and target tables in a cloud bulk load, the bulk loader (at least SQL Server Azure Bulk Loader) will fail to load the table using the bulk mechanism or will put the values in the wrong column. | ||||
Steps To Reproduce | 1. Create target SQL Server Azure database. 2. Create local H2 database. 3. Create tables where the order of columns are not the same between the source and target. 4. Use the BULK INSERT mechanism of bulk load. 5. The values will show up in the wrong columns in the target table, or the bulk load will fail and fall back to default loading. | ||||
Tags | bulk, initial/partial load | ||||
Date Modified | Username | Field | Change |
---|---|---|---|
2023-04-21 19:56 | pmarzullo | New Issue | |
2023-04-21 19:56 | pmarzullo | Status | new => assigned |
2023-04-21 19:56 | pmarzullo | Assigned To | => pmarzullo |
2023-04-21 19:56 | pmarzullo | Tag Attached: bulk | |
2023-04-21 19:56 | pmarzullo | Tag Attached: initial/partial load | |
2023-04-21 20:09 | pmarzullo | Status | assigned => resolved |
2023-04-21 20:09 | pmarzullo | Resolution | open => fixed |
2023-04-21 20:09 | pmarzullo | Fixed in Version | => 3.14.7 |
2023-05-12 19:49 | admin | Status | resolved => closed |