Varchar limits are probably too low and/or need better enforcement

[MoralCode]

ClassClockAPI/common/db_schema.py

Line 46 in fa35cfe

display_name = db.Column('bell_schedule_display_name', db.VARCHAR(length=75))

as an example of the one that was causing issues (edit: its the 20 character limit on BellScheduleDisplayName thats causing issues)

it seems this is currently being enforced/caught at the sqlalchemy layer by as a DataError. which is probably a dumb way to do it

pending further evaluation and root-causing as the affected column ((mysql.connector.errors.DataError) 1406 (22001): Data too long for column 'bell_schedule_display_name' at row 1) wasnt being given a string that was too long (only 27 ASCII characters). This will also likely require a schema change

[MoralCode]

Sentry incident refs: CLASSCLOCK-API-7 CLASSCLOCK-API-9

can confirm this crash is replicable when the display name is too long (such as "this is a really long display name for testing purposes")

[MoralCode]

added client side validation in MoralCode/ClassClock@47ffde1 to make this less likely to happen. still needs to be fixed at the schema level though