Command Syntax
Prerequisites
- Administrative access to VillageSQL
- No tables using custom types from the extension
- Backup of data if extension stores custom data
Uninstall Steps
1. Attempt Uninstall
Run the uninstall command. If the extension has no dependencies, it will succeed immediately. If columns depend on it, the error message identifies exactly which ones:2. Uninstall the Extension
- ✅ All VDFs (functions) provided by the extension
- ✅ Custom type definitions registered by the extension
- ✅ Extension registration record
- ✅ Custom column metadata for the extension
- ❌ The
.vebfile remains inveb_dir - ❌ Expanded directories in
_expanded/remain temporarily - ❌ Table data (you must drop tables with custom types first)
Expansion directories in
_expanded/{extension}/{sha256}/ are cleaned up automatically on server restart.3. Verify Uninstall
Common Errors
| Error | Cause | Solution |
|---|---|---|
Cannot drop extension \name` as N column(s) depend on it, e.g. db.table.col has type TYPE` | Tables have columns using the extension’s custom types | Drop or alter the identified columns, then retry |
Extension not found | Extension not installed | Verify with SELECT * FROM INFORMATION_SCHEMA.EXTENSIONS |
Optional: Remove .veb File
The.veb file remains after uninstall. To remove completely:
The .veb file can be kept safely for future reinstallation. Deleting it does not affect server performance.
Reinstalling
To reinstall an extension, useINSTALL EXTENSION again (if .veb file still exists):
Next Steps
Install Extensions
Add extensions back if needed
Managing Extensions
Monitor and troubleshoot extensions
System Reference
Query system tables

