We really don’t want to worry or rely too much on IDs as they are the Databases language, so we as humans want to instead use “keys” for everything which get translated into the IDs. This takes just a bit of extra query but it saves us from having to remember arbitrary number/id associations.
What are the fields that each table must have?
tbl.is_base_fields:
key
name
created_at
created_by
created_form
created_action
updated_at
updated_by
migration_id
deleted (soft-delete)
deleted_at
deleted_by
Addresses, Emails and Phone Numbers
active (bit)
[base-fields]
type (label)
primary
billing
ord
verified
archive_by
archive_at
Table (table containing all the recs of Tables)
Table Creation
We use separate procs to enter table recs (p_table_add) and then another one to actually create the table so we could have a table record without an actual db-table, but when we run the p_table_create then it creates is or it will make sure an existing table has all of our base fields
Table-Alias
? Use tbl_alias table (with title, key, ord, fltr, join-x) in order to make it so we don’t duplicate the tbl recs which have a lot of properties. So when we pull the list of tables we do it via a query that uses “union all” and joins the tables
Want to print your doc? This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
