Skip Navigation

[Resuelto] Information of MySQL tables

This support ticket is created hace 4 años, 11 meses. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Hoy no hay técnicos de soporte disponibles en el foro Juego de herramientas. Siéntase libre de enviar sus tiques y les daremos trámite tan pronto como estemos disponibles en línea. Gracias por su comprensión.

Sun Mon Tue Wed Thu Fri Sat
8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 - -
13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 - -

Supporter timezone: America/New_York (GMT-04:00)

Etiquetado: 

Este tema contiene 2 respuestas, tiene 2 mensajes.

Última actualización por luisH-3 hace 4 años, 11 meses.

Asistido por: Christian Cox.

Autor
Mensajes
#1427869

Good morning I would need to be provided with information about the following MySQL tables that Toolset has created in my WordPress database. I would like to know what each table is for and what the fields in those tables are.
The tables are:
- wp_toolset_associations
- wp_toolset_post_guid_id
- wp_toolset_relationships
- wp_toolset_type_sets
- wp_toolset_maps_address_cache

I await your response.
Greetings and thank you very much.

#1430379

Hello. I can tell you general information about each table and provide you with the create syntax. This should provide structural information about the individual fields included in the table.

- wp_toolset_associations
relational table that holds information about each relationship established between posts, including the post relationship ID, the parent and child post IDs, and the intermediary post ID if one exists.

CREATE TABLE `wp_toolset_associations` (
  `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `relationship_id` bigint(20) unsigned NOT NULL,
  `parent_id` bigint(20) unsigned NOT NULL,
  `child_id` bigint(20) unsigned NOT NULL,
  `intermediary_id` bigint(20) unsigned NOT NULL,
  PRIMARY KEY (`id`),
  KEY `relationship_id` (`relationship_id`),
  KEY `parent_id` (`parent_id`,`relationship_id`),
  KEY `child_id` (`child_id`,`relationship_id`)
) ENGINE=InnoDB AUTO_INCREMENT=89 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

- wp_toolset_relationships
table that holds information about each post relationship, like the name and slug, which post types are involved, the role names assigned to the posts in this relationship, and information about the maximum number of each post allowed.

CREATE TABLE `wp_toolset_relationships` (
  `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `slug` varchar(190) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
  `display_name_plural` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
  `display_name_singular` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
  `driver` varchar(50) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
  `parent_domain` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
  `parent_types` bigint(20) unsigned NOT NULL DEFAULT '0',
  `child_domain` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
  `child_types` bigint(20) unsigned NOT NULL DEFAULT '0',
  `intermediary_type` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
  `ownership` varchar(8) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT 'none',
  `cardinality_parent_max` int(10) NOT NULL DEFAULT '-1',
  `cardinality_parent_min` int(10) NOT NULL DEFAULT '0',
  `cardinality_child_max` int(10) NOT NULL DEFAULT '-1',
  `cardinality_child_min` int(10) NOT NULL DEFAULT '0',
  `is_distinct` tinyint(1) NOT NULL DEFAULT '0',
  `scope` longtext COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `origin` varchar(50) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
  `role_name_parent` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
  `role_name_child` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
  `role_name_intermediary` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
  `role_label_parent_singular` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
  `role_label_child_singular` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
  `role_label_parent_plural` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
  `role_label_child_plural` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
  `needs_legacy_support` tinyint(1) NOT NULL DEFAULT '0',
  `is_active` tinyint(1) NOT NULL DEFAULT '0',
  `autodelete_intermediary` tinyint(1) NOT NULL DEFAULT '1',
  PRIMARY KEY (`id`),
  KEY `slug` (`slug`),
  KEY `is_active` (`is_active`),
  KEY `needs_legacy_support` (`needs_legacy_support`),
  KEY `parent_type` (`parent_domain`,`parent_types`),
  KEY `child_type` (`child_domain`,`child_types`)
) ENGINE=InnoDB AUTO_INCREMENT=100 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

- wp_toolset_post_guid_id
a relational table that relates an image's guid to its post id, to support custom image field values

CREATE TABLE `wp_toolset_post_guid_id` (
  `guid` varchar(190) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
  `post_id` bigint(20) DEFAULT NULL,
  UNIQUE KEY `post_id` (`post_id`),
  KEY `guid` (`guid`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

- wp_toolset_type_sets
a table used by the many-to-many post relationships api to support references to post type slugs

CREATE TABLE `wp_toolset_type_sets` (
  `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `set_id` bigint(20) unsigned NOT NULL DEFAULT '0',
  `type` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
  PRIMARY KEY (`id`),
  KEY `set_id` (`set_id`),
  KEY `type` (`type`)
) ENGINE=InnoDB AUTO_INCREMENT=409 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

- wp_toolset_maps_address_cache
A cache of address field values optimized for distance filter calculations. After a location is geocoded, its latitude, longitude, and formatted address will be cached here for future reference to save costly API hits and to make distance filter calculations possible

CREATE TABLE `wp_toolset_maps_address_cache` (
  `address_passed` varchar(250) COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `address` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `point` point NOT NULL,
  PRIMARY KEY (`address_passed`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;
#1431203

Resolved, thank you very much.
Greetings.