Designate/Blueprints/Records Table Redesign
< Designate | Blueprints
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.
At this time, the migration of data from the existing Records table to the new separate tables is not included in this specification document.
Database Schema Changes - WIP
The existing Records table would become obsolete and be replaced with new tables for each record type.
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 |
