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.
Database Schema Changes
The existing Records table would become obsolete.
Records
| Name | Data Type | Length | Nullable | Details |
|---|---|---|---|---|
| id | CHAR | 32 | False | Primary Key, Generated UUID |
| 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 |
| Example | Example | Example | Example | Example |
| Example | Example | Example | Example | Example |
| Example | Example | Example | Example | Example |
