Table: `ndb.hiatuschronology`#

Description#

No description available in database.

TODO: Expand this description with: - What data does this table store? - What is the business/research purpose? - How is this data collected or generated? - Are there any important caveats or data quality issues?

Table Structure#

Schema: ndb | Table Comment: No description available

Statistics#

Metric	Value
Row Count	215
Total Size	64 kB
Table Size	16 kB
Indexes Size	16 kB

Relationships#

Foreign Keys:

chronologyid → chronologies.chronologyid
hiatusid → hiatuses.hiatusid

Referenced By:

TODO: Document which tables reference this table (will be auto-detected in validation).

Data Dictionary#

Column	Type	Nullable	Default	Constraints
`hiatusid`	integer	✓	`-`	UNIQUE, FOREIGN KEY
`chronologyid`	integer	✓	`-`	FOREIGN KEY, UNIQUE
`hiatuslength`	integer	✓	`-`	CHECK
`hiatusuncertainty`	integer	✓	`-`	-

TODO: Review column descriptions and add comments where missing.

Usage Examples#

Example 1: Basic Selection#

-- Get recent records from hiatuschronology
SELECT *
FROM hiatuschronology
ORDER BY hiatusid DESC
LIMIT 10;

Purpose: Retrieve the 10 most recent records from hiatuschronology

Example 2: Count Records#

-- Count total records
SELECT COUNT(*) as total_records
FROM hiatuschronology;

Purpose: Get the total number of records in hiatuschronology

Example 3: Join with chronologies#

-- Join with related table
SELECT 
    t1.*,
    t2.*
FROM hiatuschronology t1
INNER JOIN chronologies t2 
    ON t1.chronologyid = t2.chronologyid
LIMIT 100;

Purpose: Retrieve hiatuschronology records with related data from chronologies

Example 4: Aggregate Data#

-- Aggregate records by chronologyid
SELECT 
    chronologyid,
    COUNT(*) as count
FROM hiatuschronology
GROUP BY chronologyid
ORDER BY count DESC
LIMIT 10;

Purpose: Count records grouped by chronologyid

TODO: Add more specific examples relevant to common research questions or operational tasks.

Data Quality Notes#

TODO: Document: - Known data quality issues - Validation rules - Expected data ranges - Update frequency and mechanisms - Any ETL processes that populate this table

Maintenance#

Data Owner: TODO: Assign owner
Update Frequency: TODO: Document frequency
Last Major Schema Change: TODO: Document when schema last changed

Table: ndb.hiatuschronology#