Difference between revisions of "Designate/Blueprints/Records Table Redesign"
< Designate | Blueprints
(→Records) |
(→Records) |
||
Line 13: | Line 13: | ||
The existing Records table would become obsolete. | The existing Records table would become obsolete. | ||
− | ==== Records ==== | + | ==== Existing Records Table ==== |
{| class="wikitable" | {| class="wikitable" | ||
|- | |- |
Revision as of 22:52, 17 March 2014
Overview
Gerrit Patch | [] |
---|---|
Launchpad Blueprint | [1] |
This blueprint proposes to subdivide the Records table, which includes all record types, into a table per record type. For instance, an "a_records" table for A records, "mx_records" table for MX records, and so on.
Database Schema Changes
The existing Records table would become obsolete.
Existing Records Table
Name | Data Type | Length | Nullable | Details |
---|---|---|---|---|
id | CHAR | 32 | False | Primary Key, Generated UUID |
created_at | DATETIME | - | False | UTC time of creation |
updated_at | DATETIME | - | False | UTC time of last update |
version | INTEGER | 11 | False | Designate API version |
Example | Example | Example | Example | Example |
Example | Example | Example | Example | Example |
Example | Example | Example | Example | Example |
Example | Example | Example | Example | Example |
Example | Example | Example | Example | Example |
Example | Example | Example | Example | Example |
Example | Example | Example | Example | Example |
Example | Example | Example | Example | Example |
Example | Example | Example | Example | Example |
Example | Example | Example | Example | Example |
Example | Example | Example | Example | Example |
Example | Example | Example | Example | Example |
Example | Example | Example | Example | Example |
Example | Example | Example | Example | Example |
Example | Example | Example | Example | Example |
Example | Example | Example | Example | Example |