data-schemas issueshttps://gitlab.akamu.de/akamu/data-schemas/-/issues2021-12-07T19:25:57+01:00https://gitlab.akamu.de/akamu/data-schemas/-/issues/7Missing unique constraint for user_pool table2021-12-07T19:25:57+01:00Frederik WegnerMissing unique constraint for user_pool tableA unique constraint, index or primary keys need to be added to the user_pool table.A unique constraint, index or primary keys need to be added to the user_pool table.https://gitlab.akamu.de/akamu/data-schemas/-/issues/6Create settings to store experience required to unlock a specific level2021-05-20T17:25:54+02:00Max GranzowCreate settings to store experience required to unlock a specific levelAdd the experience required to unlock a specific level as a setting to the database.
The backend server progress for the endpoint is tracked in [game-server-go!116](https://gitlab.akamu.de/akamu/game-server-go/-/merge_requests/116).
The ...Add the experience required to unlock a specific level as a setting to the database.
The backend server progress for the endpoint is tracked in [game-server-go!116](https://gitlab.akamu.de/akamu/game-server-go/-/merge_requests/116).
The SQL query is outlined [here](https://gitlab.akamu.de/akamu/game-server-go/-/merge_requests/116#note_2285):
> ```sql
> REPLACE `setting` (`KEY`, `TYPE`, `VALUE_INT`) VALUES ("game.user.level-experience.level1", "int", 0), ("game.user.level-experience.level2", "int", 4), ("game.user.level-experience.level3", "int", 28), ("game.user.level-experience.level4", "int", 92), ("game.user.level-experience.level5", "int", 218), ("game.user.level-experience.level6", "int", 425), ("game.user.level-experience.level7", "int", 735), ("game.user.level-experience.level8", "int", 1167), ("game.user.level-experience.level9", "int", 1741), ("game.user.level-experience.level10", "int", 2479), ("game.user.level-experience.level11", "int", 3400), ("game.user.level-experience.level12", "int", 4526), ("game.user.level-experience.level13", "int", 5876), ("game.user.level-experience.level14", "int", 7470), ("game.user.level-experience.level15", "int", 9330), ("game.user.level-experience.level16", "int", 11475), ("game.user.level-experience.level17", "int", 13927), ("game.user.level-experience.level18", "int", 16705), ("game.user.level-experience.level19", "int", 19829), ("game.user.level-experience.level20", "int", 23321), ("game.user.level-experience.level21", "int", 27200), ("game.user.level-experience.level22", "int", 31488), ("game.user.level-experience.level23", "int", 36204), ("game.user.level-experience.level24", "int", 41368), ("game.user.level-experience.level25", "int", 47002), ("game.user.level-experience.level26", "int", 53125), ("game.user.level-experience.level27", "int", 59759), ("game.user.level-experience.level28", "int", 66923), ("game.user.level-experience.level29", "int", 74637), ("game.user.level-experience.level30", "int", 82923)
> ```https://gitlab.akamu.de/akamu/data-schemas/-/issues/5Subject duplcates possible2021-05-19T06:45:17+02:00Frederik WegnerSubject duplcates possibleThere should be unique constraints on subject name and shortname fields.There should be unique constraints on subject name and shortname fields.https://gitlab.akamu.de/akamu/data-schemas/-/issues/4Make all fields of university required2021-03-05T18:19:06+01:00Julien SchröterMake all fields of university requiredServer execution fails if any field of the university table is nullServer execution fails if any field of the university table is nullJulien SchröterJulien Schröterhttps://gitlab.akamu.de/akamu/data-schemas/-/issues/2Useranswer timestamp field2020-12-29T14:44:23+01:00Frederik WegnerUseranswer timestamp fieldAdd a timestamp field `created` to the table `useranswer`. It should default to the time of insertion.Add a timestamp field `created` to the table `useranswer`. It should default to the time of insertion.