/usr/share/doc/cpanel-pdns
NameSizeModeActions
3.4.0_to_4.0.0_schema.sqlite3.sql54680644editdlrm
3.4.0_to_4.1.0_schema.mysql.sql8330644editdlrm
4.0.0_to_4.2.0_schema.sqlite3.sql17020644editdlrm
4.1.0_to_4.2.0_schema.mysql.sql1160644editdlrm
4.2.0_to_4.3.0_schema.mysql.sql710644editdlrm
4.2.0_to_4.3.0_schema.sqlite3.sql6060644editdlrm
4.3.0_to_4.3.1_schema.sqlite3.sql5080644editdlrm
4.3.0_to_4.7.0_schema.mysql.sql2200644editdlrm
4.3.1_to_4.7.0_schema.sqlite3.sql2720644editdlrm
COPYING180910644editdlrm
dnssec-3.x_to_3.4.0_schema.mysql.sql15830644editdlrm
dnssec-3.x_to_3.4.0_schema.sqlite3.sql35410644editdlrm
enable-foreign-keys.mysql.sql11100644editdlrm
nodnssec-3.x_to_3.4.0_schema.mysql.sql20470644editdlrm
nodnssec-3.x_to_3.4.0_schema.sqlite3.sql23360644editdlrm
README56870644editdlrm
schema.mysql.sql31390644editdlrm
schema.sqlite3.sql31930644editdlrm
Edit: /usr/share/doc/cpanel-pdns/enable-foreign-keys.mysql.sql (1110B)
/* Using this SQL causes Mysql to create foreign keys on your database. This will make sure that no records, comments or keys exists for domains that you already removed. This is not enabled by default, because we're not sure what the consequences are from a performance point of view. If you do have feedback, please let us know how this affects your setup. Please note that it's not possible to apply this, before you cleaned up your database, as the foreign keys do not exist. */ ALTER TABLE records ADD CONSTRAINT `records_domain_id_ibfk` FOREIGN KEY (`domain_id`) REFERENCES `domains` (`id`) ON DELETE CASCADE ON UPDATE CASCADE; ALTER TABLE comments ADD CONSTRAINT `comments_domain_id_ibfk` FOREIGN KEY (`domain_id`) REFERENCES `domains` (`id`) ON DELETE CASCADE ON UPDATE CASCADE; ALTER TABLE domainmetadata ADD CONSTRAINT `domainmetadata_domain_id_ibfk` FOREIGN KEY (`domain_id`) REFERENCES `domains` (`id`) ON DELETE CASCADE ON UPDATE CASCADE; ALTER TABLE cryptokeys ADD CONSTRAINT `cryptokeys_domain_id_ibfk` FOREIGN KEY (`domain_id`) REFERENCES `domains` (`id`) ON DELETE CASCADE ON UPDATE CASCADE;