Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 2.4.0
-
Component/s: None
-
Labels:None
-
Number of attachments :
Description
When initial.load.delete.first=true, the table metadata written out to CSV didn't use the target settings in sym_router. Because the initial load did use the target settings, a different table name was written and because the trigger history id was the same, the column metadata was not written.
See http://sourceforge.net/projects/symmetricds/forums/forum/739236/topic/4607504
The solution is to pass the router id to the purge event.
Activity
Chris Henson
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Status | Open [ 1 ] | In Progress [ 3 ] |
Chris Henson
made changes -
| Status | In Progress [ 3 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
Chris Henson
made changes -
| Description |
When initial.load.delete.first=true, the table metadata written out to CSV didn't use the target settings in sym_router. Because the initial load did use the target settings, a different table name was written and because the trigger history id was the same, the column metadata was not written. Table metadata should not be written for a SQL event anyways, so the solution is to not write the table metadata for SQL events.
See http://sourceforge.net/projects/symmetricds/forums/forum/739236/topic/4607504 |
When initial.load.delete.first=true, the table metadata written out to CSV didn't use the target settings in sym_router. Because the initial load did use the target settings, a different table name was written and because the trigger history id was the same, the column metadata was not written.
See http://sourceforge.net/projects/symmetricds/forums/forum/739236/topic/4607504 The solution is to pass the router id to the purge event. |
Chris Henson
made changes -
| Status | Resolved [ 5 ] | Closed [ 6 ] |
| Assignee | Chris Henson [ chenson42 ] |