PowerDNS OpenDBX Backend/Migration - Revision history

Nose: removed backlink

2008-06-22T12:39:04Z

removed backlink

Nose at 18:06, 8 March 2008

2008-03-08T18:06:08Z

Nose: migration

2007-11-18T15:12:13Z

migration

New page

To convert an existing gMySQL Database to an OpenDBX MySQL database, an additional status column is required since patch 2.9.20-3:

ALTER TABLE domains ADD ( status CHAR(1) NOT NULL DEFAULT 'A' )

Adding a foreign key constraint from records.domain_id to domains.id is a good idea too:

ALTER TABLE records ADD CONSTRAINT fk_records_domainid
FOREIGN KEY (domain_id) REFERENCES domains (id)
ON UPDATE CASCADE ON DELETE CASCADE

You should also recreate your indices for optimal performance. Please have a look in the appropriate file listed in the section above.

----
Back to [[PowerDNS_OpenDBX_Backend|Overview]]

← Older revision		Revision as of 12:39, 22 June 2008
Line 19:		Line 19:

	ALTER TABLE "domains" ADD "auto_serial" INTEGER DEFAULT 0;		ALTER TABLE "domains" ADD "auto_serial" INTEGER DEFAULT 0;
−
−
−	~~----~~
−	~~Back to [[PowerDNS_OpenDBX_Backend\|Overview]]~~

@@ Line 1: / Line 1: @@
 To convert an existing gMySQL Database to an OpenDBX MySQL database, an additional status column is required since patch 2.9.20-3:
-  ALTER TABLE domains ADD ( status CHAR(1) NOT NULL DEFAULT 'A' )
+ SET SESSION sql_mode='ANSI';
 Adding a foreign key constraint from records.domain_id to domains.id is a good idea too:
-  ALTER TABLE records ADD CONSTRAINT fk_records_domainid
+  ALTER TABLE "records" ADD CONSTRAINT "pdns_fk_records_domainid"
-  FOREIGN KEY (domain_id) REFERENCES domains (id)
+  FOREIGN KEY ("domain_id") REFERENCES "domains" ("id")
   ON UPDATE CASCADE ON DELETE CASCADE
 You should also recreate your indices for optimal performance. Please have a look in the appropriate file listed in the section above.
 ----
 Back to [[PowerDNS_OpenDBX_Backend|Overview]]