Database Storage - Githubissues

UniRegensburg / unsere-app-fur-die-universitat-regensburg-bib-buddy

Bib Buddy - deine App für eine konzentrierte, offene Literaturarbeit!

0 stars 0 forks source link

Database Storage #33

Closed SarahKurek closed 3 years ago

SarahKurek commented 3 years ago

database_er_diagramm

SarahKurek commented 3 years ago

This is the updated ER-diagram for the data storage.

claudia3 commented 3 years ago

I have some questions concerning the storage:

Should we save the picture in the gallery or directly add it into the internal storage of the app?
What should we do when a user renames a picture in the gallery? If it happens the path to the picture in the database doesn't exist anymore or is false.

SarahKurek commented 3 years ago

In my opinion it is better to store the images and files in the database because you have no problems with changing file paths. The resulting additional SQL queries are practically no more effort.

SarahKurek commented 3 years ago

I checked out other projects. These store images and files in the database to avoid emerging problems of a hard coded path. So I reworked the database structure again. In addition, I have named the columns consistently and added a table for the note_type as a look-up-table. Below is the updated ER diagram.

SarahKurek commented 3 years ago

database_er_diagramm_new

LuisMossburger commented 3 years ago

To Do: Either link table between "book" and "note" or "book_id" in table "note" instead of "note_id" in table "book"

SarahKurek commented 3 years ago

newERDiagramm Updated ER diagram