DB table structure on Multisite (GDPR compliance)
-
Hey Milan,
we run several multisite installations and gave your plugin a try.
First thing we were a bit irritated by is the database design. Is it correct and intentional that all sites will share the same four databse tables?wp_gdmaq_emails wp_gdmaq_log wp_gdmaq_log_email wp_gdmaq_queueAs we run seperate clients on one multisite installation, we have to enforce logical data separation following GDPR requirements when working with personal information. Having all data stored in one table will not comply with these legal requirements.
In addition to the legal aspect the single table approach makes housekeeping quite hard. In particular deleting a site and all its prefixed tables will not prune all the related entries from your global tables. As the plugin deactivation routines will not run on site deletion.
Is there any way to run your plugin in a “one set of tables per site” mode?
Which would then use a table structure like this:
wp_2_gdmaq_emails wp_2_gdmaq_log wp_2_gdmaq_log_email wp_2_gdmaq_queue wp_3_gdmaq_emails wp_3_gdmaq_log wp_3_gdmaq_log_email wp_3_gdmaq_queueThanks and best regards,
Jan
The topic ‘DB table structure on Multisite (GDPR compliance)’ is closed to new replies.