You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem with adding structured data is that the database we're updating has a simple VARCHAR(75) column for office hours, meaning we can only store simple text up to 75 characters.
We can discuss the possibility of storing more structured or meaningful data, since we're moving this to entirely within 360, but that's a bigger question that's probably outside the scope of this initial pull request.
Faculty/Professor office hours are currently stored as VARCHAR(75) in SQL. This causes possible user errors which could be prevented if we had an organized/structured input. This would require a change in SQL, API, UI
The text was updated successfully, but these errors were encountered:
The problem with adding structured data is that the database we're updating has a simple
VARCHAR(75)
column for office hours, meaning we can only store simple text up to 75 characters.We can discuss the possibility of storing more structured or meaningful data, since we're moving this to entirely within 360, but that's a bigger question that's probably outside the scope of this initial pull request.
Originally posted by @EjPlatzer in gordon-cs/gordon-360-ui#1871 (comment)
TLDR;
Faculty/Professor office hours are currently stored as VARCHAR(75) in SQL. This causes possible user errors which could be prevented if we had an organized/structured input. This would require a change in SQL, API, UI
The text was updated successfully, but these errors were encountered: