wp_banman
StaticStores banman data created by this plugin.
Column Definitions
| Column | Type | Nullable |
|---|---|---|
| 🔑id | int(11) | NO |
| position | varchar(30) | NO |
| name | varchar(255) | NO |
| type | tinyint(1) | NO |
| attach_id | int(11) | NO |
| code | text | NO |
| url | varchar(255) | YES |
| show_start | date | NO |
| show_end | date | NO |
| ordering | int(11) | NO |
| show_count | int(11) | NO |
| click_count | int(11) | NO |
| params | text | NO |
| publish | tinyint(1) | NO |
CREATE TABLE Statement
CREATE TABLE IF NOT EXISTS `wp_banman` ( `id` int(11) NOT NULL AUTO_INCREMENT, `position` varchar(30) NOT NULL, `name` varchar(255) NOT NULL, `type` tinyint(1) NOT NULL, `attach_id` int(11) NOT NULL, `code` text NOT NULL, `url` varchar(255) DEFAULT NULL, `show_start` date NOT NULL, `show_end` date NOT NULL, `ordering` int(11) NOT NULL, `show_count` int(11) NOT NULL, `click_count` int(11) NOT NULL, `params` text NOT NULL, `publish` tinyint(1) NOT NULL, PRIMARY KEY (`id`) ) ENGINE
Safe to delete?
If you have uninstalled BanMan, this table is generally safe to remove. However, always back up your database first.
Note: Some plugins share tables or are dependencies of other plugins. Verify nothing else depends on this table before dropping it.
How to remove this table
DROP TABLE IF EXISTS `wp_banman`;
Run this query using phpMyAdmin, Adminer, or your MySQL client. Back up first.