$conf, $runtime; function_exists('chdir') AND chdir(APP_PATH); $r = 'mysql' == $conf['cache']['type'] ? website_set('runtime', $runtime) : cache_set('runtime', $runtime); } function runtime_truncate() { global $conf; 'mysql' == $conf['cache']['type'] ? website_set('runtime', '') : cache_delete('runtime'); } register_shutdown_function('runtime_save'); ?>Constraints in custom tables for plugin development - Yes or No?|Programmer puzzle solving
最新消息:Welcome to the puzzle paradise for programmers! Here, a well-designed puzzle awaits you. From code logic puzzles to algorithmic challenges, each level is closely centered on the programmer's expertise and skills. Whether you're a novice programmer or an experienced tech guru, you'll find your own challenges on this site. In the process of solving puzzles, you can not only exercise your thinking skills, but also deepen your understanding and application of programming knowledge. Come to start this puzzle journey full of wisdom and challenges, with many programmers to compete with each other and show your programming wisdom! Translated with DeepL.com (free version)

Constraints in custom tables for plugin development - Yes or No?

matteradmin11PV0评论

After a longer web search, I still don't know, whether I should use constraints in my custom tables for WordPress plugin development. The most of my custom tables have a relation to the {prefix}users table with a foreign key user_id referring to the ID of {prefix}users. In common database design I would make a sql query like this example:

CREATE TABLE IF NOT EXISTS `{prefix}logs` (
`user_id` INT UNSIGNED  NOT NULL,
[...]
PRIMARY KEY  (`user_id`),
CONSTRAINT `logs_ibfk_1` 
FOREIGN KEY (`user_id`)
REFERENCES `{prefix}users` (`ID`)
ON UPDATE CASCADE 
ON DELETE CASCADE)
CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;

For WordPress don't make use of constraints due to the specific database design of WordPress core, I'm not sure whether to use for my plugin or not.

Post a comment

comment list (0)

  1. No comments so far