Created
August 2, 2024 03:11
-
-
Save Aaron2963/48f0677bea69d7d2d01fda60f9453b31 to your computer and use it in GitHub Desktop.
wordpress db schema
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
CREATE TABLE `wp_bv_fw_requests` ( | |
`id` bigint(20) NOT NULL AUTO_INCREMENT, | |
`ip` varchar(50) NOT NULL DEFAULT '', | |
`status` int(1) NOT NULL DEFAULT 0, | |
`time` bigint(20) NOT NULL DEFAULT 1388516401, | |
`path` varchar(100) NOT NULL DEFAULT '', | |
`host` varchar(100) NOT NULL DEFAULT '', | |
`method` varchar(100) NOT NULL DEFAULT '', | |
`resp_code` int(6) NOT NULL DEFAULT 0, | |
`category` int(1) NOT NULL DEFAULT 4, | |
`referer` varchar(200) NOT NULL DEFAULT '', | |
`user_agent` varchar(200) NOT NULL DEFAULT '', | |
`filenames` text DEFAULT NULL, | |
`query_string` text DEFAULT NULL, | |
`rules_info` text DEFAULT NULL, | |
`request_id` varchar(200) DEFAULT NULL, | |
`matched_rules` text DEFAULT NULL, | |
PRIMARY KEY (`id`) | |
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
CREATE TABLE `wp_bv_ip_store` ( | |
`id` bigint(20) NOT NULL AUTO_INCREMENT, | |
`start_ip_range` varbinary(16) NOT NULL, | |
`end_ip_range` varbinary(16) NOT NULL, | |
`is_fw` tinyint(1) NOT NULL, | |
`is_lp` tinyint(1) NOT NULL, | |
`type` int(1) NOT NULL, | |
`is_v6` tinyint(1) NOT NULL DEFAULT 0, | |
PRIMARY KEY (`id`), | |
KEY `ip_range` (`start_ip_range`,`end_ip_range`) | |
) ENGINE=InnoDB DEFAULT CHARSET=binary; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
CREATE TABLE `wp_bv_lp_requests` ( | |
`id` bigint(20) NOT NULL AUTO_INCREMENT, | |
`ip` varchar(50) NOT NULL DEFAULT '', | |
`status` int(1) NOT NULL DEFAULT 0, | |
`username` varchar(50) NOT NULL DEFAULT '', | |
`message` varchar(100) NOT NULL DEFAULT '', | |
`category` int(1) NOT NULL DEFAULT 0, | |
`time` bigint(20) NOT NULL DEFAULT 1388516401, | |
`request_id` varchar(200) DEFAULT NULL, | |
PRIMARY KEY (`id`) | |
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
CREATE TABLE `wp_commentmeta` ( | |
`meta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, | |
`comment_id` bigint(20) unsigned NOT NULL DEFAULT 0, | |
`meta_key` varchar(255) DEFAULT NULL, | |
`meta_value` longtext DEFAULT NULL, | |
PRIMARY KEY (`meta_id`), | |
KEY `comment_id` (`comment_id`), | |
KEY `meta_key` (`meta_key`(191)) | |
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
CREATE TABLE `wp_comments` ( | |
`comment_ID` bigint(20) unsigned NOT NULL AUTO_INCREMENT, | |
`comment_post_ID` bigint(20) unsigned NOT NULL DEFAULT 0, | |
`comment_author` tinytext NOT NULL, | |
`comment_author_email` varchar(100) NOT NULL DEFAULT '', | |
`comment_author_url` varchar(200) NOT NULL DEFAULT '', | |
`comment_author_IP` varchar(100) NOT NULL DEFAULT '', | |
`comment_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', | |
`comment_date_gmt` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', | |
`comment_content` text NOT NULL, | |
`comment_karma` int(11) NOT NULL DEFAULT 0, | |
`comment_approved` varchar(20) NOT NULL DEFAULT '1', | |
`comment_agent` varchar(255) NOT NULL DEFAULT '', | |
`comment_type` varchar(20) NOT NULL DEFAULT 'comment', | |
`comment_parent` bigint(20) unsigned NOT NULL DEFAULT 0, | |
`user_id` bigint(20) unsigned NOT NULL DEFAULT 0, | |
PRIMARY KEY (`comment_ID`), | |
KEY `comment_post_ID` (`comment_post_ID`), | |
KEY `comment_approved_date_gmt` (`comment_approved`,`comment_date_gmt`), | |
KEY `comment_date_gmt` (`comment_date_gmt`), | |
KEY `comment_parent` (`comment_parent`), | |
KEY `comment_author_email` (`comment_author_email`(10)) | |
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
CREATE TABLE `wp_links` ( | |
`link_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, | |
`link_url` varchar(255) NOT NULL DEFAULT '', | |
`link_name` varchar(255) NOT NULL DEFAULT '', | |
`link_image` varchar(255) NOT NULL DEFAULT '', | |
`link_target` varchar(25) NOT NULL DEFAULT '', | |
`link_description` varchar(255) NOT NULL DEFAULT '', | |
`link_visible` varchar(20) NOT NULL DEFAULT 'Y', | |
`link_owner` bigint(20) unsigned NOT NULL DEFAULT 1, | |
`link_rating` int(11) NOT NULL DEFAULT 0, | |
`link_updated` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', | |
`link_rel` varchar(255) NOT NULL DEFAULT '', | |
`link_notes` mediumtext NOT NULL, | |
`link_rss` varchar(255) NOT NULL DEFAULT '', | |
PRIMARY KEY (`link_id`), | |
KEY `link_visible` (`link_visible`) | |
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
CREATE TABLE `wp_options` ( | |
`option_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, | |
`option_name` varchar(191) NOT NULL DEFAULT '', | |
`option_value` longtext NOT NULL, | |
`autoload` varchar(20) NOT NULL DEFAULT 'yes', | |
PRIMARY KEY (`option_id`), | |
UNIQUE KEY `option_name` (`option_name`), | |
KEY `autoload` (`autoload`) | |
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
CREATE TABLE `wp_postmeta` ( | |
`meta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, | |
`post_id` bigint(20) unsigned NOT NULL DEFAULT 0, | |
`meta_key` varchar(255) DEFAULT NULL, | |
`meta_value` longtext DEFAULT NULL, | |
PRIMARY KEY (`meta_id`), | |
KEY `post_id` (`post_id`), | |
KEY `meta_key` (`meta_key`(191)) | |
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
CREATE TABLE `wp_posts` ( | |
`ID` bigint(20) unsigned NOT NULL AUTO_INCREMENT, | |
`post_author` bigint(20) unsigned NOT NULL DEFAULT 0, | |
`post_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', | |
`post_date_gmt` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', | |
`post_content` longtext NOT NULL, | |
`post_title` text NOT NULL, | |
`post_excerpt` text NOT NULL, | |
`post_status` varchar(20) NOT NULL DEFAULT 'publish', | |
`comment_status` varchar(20) NOT NULL DEFAULT 'open', | |
`ping_status` varchar(20) NOT NULL DEFAULT 'open', | |
`post_password` varchar(255) NOT NULL DEFAULT '', | |
`post_name` varchar(200) NOT NULL DEFAULT '', | |
`to_ping` text NOT NULL, | |
`pinged` text NOT NULL, | |
`post_modified` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', | |
`post_modified_gmt` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', | |
`post_content_filtered` longtext NOT NULL, | |
`post_parent` bigint(20) unsigned NOT NULL DEFAULT 0, | |
`guid` varchar(255) NOT NULL DEFAULT '', | |
`menu_order` int(11) NOT NULL DEFAULT 0, | |
`post_type` varchar(20) NOT NULL DEFAULT 'post', | |
`post_mime_type` varchar(100) NOT NULL DEFAULT '', | |
`comment_count` bigint(20) NOT NULL DEFAULT 0, | |
PRIMARY KEY (`ID`), | |
KEY `post_name` (`post_name`(191)), | |
KEY `type_status_date` (`post_type`,`post_status`,`post_date`,`ID`), | |
KEY `post_parent` (`post_parent`), | |
KEY `post_author` (`post_author`) | |
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
CREATE TABLE `wp_term_relationships` ( | |
`object_id` bigint(20) unsigned NOT NULL DEFAULT 0, | |
`term_taxonomy_id` bigint(20) unsigned NOT NULL DEFAULT 0, | |
`term_order` int(11) NOT NULL DEFAULT 0, | |
PRIMARY KEY (`object_id`,`term_taxonomy_id`), | |
KEY `term_taxonomy_id` (`term_taxonomy_id`) | |
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
CREATE TABLE `wp_term_taxonomy` ( | |
`term_taxonomy_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, | |
`term_id` bigint(20) unsigned NOT NULL DEFAULT 0, | |
`taxonomy` varchar(32) NOT NULL DEFAULT '', | |
`description` longtext NOT NULL, | |
`parent` bigint(20) unsigned NOT NULL DEFAULT 0, | |
`count` bigint(20) NOT NULL DEFAULT 0, | |
PRIMARY KEY (`term_taxonomy_id`), | |
UNIQUE KEY `term_id_taxonomy` (`term_id`,`taxonomy`), | |
KEY `taxonomy` (`taxonomy`) | |
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
CREATE TABLE `wp_termmeta` ( | |
`meta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, | |
`term_id` bigint(20) unsigned NOT NULL DEFAULT 0, | |
`meta_key` varchar(255) DEFAULT NULL, | |
`meta_value` longtext DEFAULT NULL, | |
PRIMARY KEY (`meta_id`), | |
KEY `term_id` (`term_id`), | |
KEY `meta_key` (`meta_key`(191)) | |
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
CREATE TABLE `wp_terms` ( | |
`term_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, | |
`name` varchar(200) NOT NULL DEFAULT '', | |
`slug` varchar(200) NOT NULL DEFAULT '', | |
`term_group` bigint(10) NOT NULL DEFAULT 0, | |
PRIMARY KEY (`term_id`), | |
KEY `slug` (`slug`(191)), | |
KEY `name` (`name`(191)) | |
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
CREATE TABLE `wp_usermeta` ( | |
`umeta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, | |
`user_id` bigint(20) unsigned NOT NULL DEFAULT 0, | |
`meta_key` varchar(255) DEFAULT NULL, | |
`meta_value` longtext DEFAULT NULL, | |
PRIMARY KEY (`umeta_id`), | |
KEY `user_id` (`user_id`), | |
KEY `meta_key` (`meta_key`(191)) | |
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
CREATE TABLE `wp_users` ( | |
`ID` bigint(20) unsigned NOT NULL AUTO_INCREMENT, | |
`user_login` varchar(60) NOT NULL DEFAULT '', | |
`user_pass` varchar(255) NOT NULL DEFAULT '', | |
`user_nicename` varchar(50) NOT NULL DEFAULT '', | |
`user_email` varchar(100) NOT NULL DEFAULT '', | |
`user_url` varchar(100) NOT NULL DEFAULT '', | |
`user_registered` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', | |
`user_activation_key` varchar(255) NOT NULL DEFAULT '', | |
`user_status` int(11) NOT NULL DEFAULT 0, | |
`display_name` varchar(250) NOT NULL DEFAULT '', | |
PRIMARY KEY (`ID`), | |
KEY `user_login_key` (`user_login`), | |
KEY `user_nicename` (`user_nicename`), | |
KEY `user_email` (`user_email`) | |
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment