Skip to content
This repository has been archived by the owner on Feb 2, 2021. It is now read-only.

Refactor database structure for better sync #24

Open
divadsn opened this issue Oct 22, 2018 · 3 comments
Open

Refactor database structure for better sync #24

divadsn opened this issue Oct 22, 2018 · 3 comments
Assignees
Labels
help wanted Extra attention is needed important This is necessary before anything else is done

Comments

@divadsn
Copy link
Member

divadsn commented Oct 22, 2018

Models should work for both systems.

@divadsn divadsn self-assigned this Oct 22, 2018
@divadsn divadsn added important This is necessary before anything else is done help wanted Extra attention is needed labels Jan 29, 2019
@divadsn
Copy link
Member Author

divadsn commented Jan 29, 2019

We might want to store only the data we need for the UI, such as first and last name, email address or birthday for accounts. The profile picture is stored seperately with own id.

@divadsn
Copy link
Member Author

divadsn commented Jan 29, 2019

See #27 for details

@divadsn
Copy link
Member Author

divadsn commented Mar 18, 2019

As I decided to not support Karta Krakowska (see #30), I will only re-do the database structure to include less private information. This will also make it easier for me to create the UI.

@divadsn divadsn changed the title Refactor database structure for both backends Refactor database structure for better sync Mar 18, 2019
divadsn added a commit that referenced this issue Apr 6, 2019
TODO: Run gradle build to see what is broken
divadsn added a commit that referenced this issue Apr 6, 2019
TODO: Run gradle build to see what is broken
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
help wanted Extra attention is needed important This is necessary before anything else is done
Projects
None yet
Development

No branches or pull requests

1 participant