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
{{ message }}
This repository has been archived by the owner on May 28, 2022. It is now read-only.
The database schema used to in the presentation table has a line UNIQUE (Speaker, Title) ON CONFLICT IGNORE which makes the Speaker, Title combination behave similar to a primary key. However, no logging is done in the Qt Client or in the database when a user tries to insert a conflicting record.
The schema should be revisited. To either redfine the primary key or to modify the software to notify the user that their speaker-title-event combination is conflicting and that they should chose a different combination.
I'm not sure if we should have the speaker-title combo as a unique constraint. Speakers often give the same talk at different events. I think the database should allow two records to exist if the speaker and title are the same, but the event is different.
The database schema used to in the presentation table has a line
UNIQUE (Speaker, Title) ON CONFLICT IGNORE
which makes the Speaker, Title combination behave similar to a primary key. However, no logging is done in the Qt Client or in the database when a user tries to insert a conflicting record.The schema should be revisited. To either redfine the primary key or to modify the software to notify the user that their speaker-title-event combination is conflicting and that they should chose a different combination.
related #619
The text was updated successfully, but these errors were encountered: