View Revisions: Issue #2993
| Summary | 0002993: ddl-utils should not drop tables when it can't update their structure | ||
|---|---|---|---|
| Revision | 2017-02-23 20:19 by mmichalek | ||
| Description | If ddl-utils detects a situation where it thinks it can't update a table structure, it will simply drop and re-create the table. This could lead to unexpected data loss. Originally the plan was to abort, but it turns out this situation occurs during an upgrade from 3.7 to 3.8: Data cannot be retained in table sym_node_communication because of the addition of the required column queue So in this situation we'll create a backup table, (sym_node_communication_), and copy the data from the old table to the backup (sym_node_communication -> sym_node_communication_) and create the new table with the new structure. A warning will be logged and for now it's up to the user to migrate the data from the backup table to the new table and cleanup the backup table. Reported on open source forum: https://sourceforge.net/p/symmetricds/discussion/739236/thread/469ff295/?limit=25#311b |
||
| Revision | 2017-02-23 20:18 by mmichalek | ||
| Description | If ddl-utils detects a situation where it thinks it can't update a table structure, it will simply drop and re-create the table. This could lead to unexpected data loss. Originally the plan was to abort, but it turns out this situation occurs during an upgrade from 3.7 to 3.8: Data cannot be retained in table sym_node_communication because of the addition of the required column queue So in this situation we'll create a backup table, (sym_node_communication_), and copy the data from the old table to the backup (sym_node_communication -> sym_node_communication_) and create the new table with the new structure. Reported on open source forum: https://sourceforge.net/p/symmetricds/discussion/739236/thread/469ff295/?limit=25#311b |
||
| Revision | 2017-02-10 14:58 by mmichalek | ||
| Description | If ddl-utils detects a situation where it thinks it can't update a table structure, it will simply drop and re-create the table. This could lead to unexpected data loss. We will change ddl-utils for now to short-circuit and not attempt any update on that table in this situation, but will throw and log an exception instead. Reported on open source forum: https://sourceforge.net/p/symmetricds/discussion/739236/thread/469ff295/?limit=25#311b |
||