View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006922 | SymmetricDS Pro | Bug | public | 2025-06-05 13:20 | 2025-06-05 21:06 |
| Reporter | josh-a-hicks | Assigned To | |||
| Priority | normal | ||||
| Status | acknowledged | Resolution | open | ||
| Product Version | 3.16.0 | ||||
| Summary | 0006922: Uninstall node action does not remove DDL capture function | ||||
| Description | Detected on SQL Server but may exist on other platforms. Turn on the DDL parameter to capture DDL changes and then uninstall the node the function : sym_on_filtered_ddl remains in place. This will cause future table creations on the database as it will fire the database level function to capture the ddl change and insert it into sym_data and reference sym_trigger_hist and they do not exist. | ||||
| Steps To Reproduce | Setup a new node connected to any database, which supports DDL capture (PostgreSQL, SQL Server, ...) and has permissions to do so. Turn on DDL capture parameter trigger.capture.ddl.changes=true Ensure DDL triggers are installed. Uninstall the node from the Manage->Nodes screen. Verify the sym_on_filtered_ddl is NOT removed (fsym_on_filtered_ddl and fsym_on_filtered_ddl_drop in PostgreSQL). To check run a simple create table script on the database and would fail to fire the function and capture the change without sym runtime tables. | ||||
| Tags | ddl/schema | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-06-05 13:20 | josh-a-hicks | New Issue | |
| 2025-06-05 13:21 | elong | Tag Attached: ddl/schema | |
| 2025-06-05 13:22 | elong | Status | new => acknowledged |
| 2025-06-05 20:48 | pbelov | Summary | Uninstall node does not remove DDL function => Uninstall node action does not remove DDL capture function |
| 2025-06-05 20:48 | pbelov | Steps to Reproduce Updated | View Revisions |
| 2025-06-05 21:06 | pbelov | Note Added: 0003014 |