docs: say SQL drops and renames move table folders and import mappings

[datlechin]

Why

Two pages say SQL leaves a table's folder and saved import mapping alone: a RENAME TABLE "drops out of its folder", and a DROP TABLE from the editor keeps the old mapping. Since #3196, a committed SQL drop or rename goes through the same table-scoped store registry as a sidebar one, and both TableFolderStorage and ImportColumnMappingStore are in it. A renamed table stays filed and keeps its mapping, and a dropped one loses both.

Change

• Sidebar folders and saved import mappings now say they follow SQL drops and renames, linking to Drop or rename with SQL for the engines and conditions.
• Drop or rename with SQL lists the folder, saved import mapping and foreign key label columns among the settings that move.

Verified

verify.sh docs passes. Checked against TableScopedSettingsRegistry.stores and CatalogEditAdoption.adoptTableRename and adoptDroppedTables.

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
TablePro	🟢 Ready	View Preview	Oct 2, 2026, 4:35 AM

💡 Tip: Enable Automations to automatically generate PRs for you.