Support an ascents table. Something like climbing-history.org would be nice to mimic.. this may entail some tables...
ascents
climber_id: int?
date: string? (represents abstract temporal unit, date, season, year, etc)
constraint, climber_id or date must be non-null
constraint, climb_id references climbers(id)
climbers
id
first-name: string
last-name: string
aliases: [string]
How would applying styles work? i.e. worked, flash, onsight, lead, top-rope, boulder, first-ascent, etc. Which of these are mutually exclusive? Does mutual exclusivity even matter?
What about shared FAs? There are plenty of routes/problems that are credited to a party (multiple climbers) with shared priority.. how can that be ensured? climber_id cannot be a part of ascents? Maybe another table ascent_parties?
Support an ascents table. Something like climbing-history.org would be nice to mimic.. this may entail some tables...
ascents
climbers
How would applying styles work? i.e. worked, flash, onsight, lead, top-rope, boulder, first-ascent, etc. Which of these are mutually exclusive? Does mutual exclusivity even matter?
What about shared FAs? There are plenty of routes/problems that are credited to a party (multiple climbers) with shared priority.. how can that be ensured?
climber_idcannot be a part ofascents? Maybe another tableascent_parties?