Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Decide on database implementation to use #13

Closed
f-fromont opened this issue Mar 10, 2022 · 2 comments
Closed

Decide on database implementation to use #13

f-fromont opened this issue Mar 10, 2022 · 2 comments
Assignees
@f-fromont
Labels
Priority: Low Something which is nice to have. Status: Available This issue is available for some to pick up. Type: Maintenance The issue is about maintenance which doesn't change the functionality of the code, e.g. refactoring
Projects
Project

Comments

@f-fromont
Copy link
Contributor

f-fromont commented Mar 10, 2022 •
edited

Describe the task that needs to be done.
As a team we need to decide the type of database that we want to use for the backend.
Currently H2 (an in memory database) is being used to allow the server to run, this was because without any database being used the spring framework used will not start up. See PR #14

Describe how a solution to your proposed task might look like (and any alternatives considered).
We could stick with the current database used: H2
We could look at implementing a different database like: mySQL (this would have the added benefits of consistency for tests)
We could also consider other database options
Notes
@f-fromont f-fromont added Priority: Medium Status: Available This issue is available for some to pick up. Type: Maintenance The issue is about maintenance which doesn't change the functionality of the code, e.g. refactoring labels Mar 10, 2022
@f-fromont f-fromont added this to To do in Project via automation Mar 10, 2022
@f-fromont f-fromont mentioned this issue Mar 10, 2022
Merged
9 tasks
@f-fromont
Copy link
Contributor Author

Discussed in backend team meeting, for now we will leave as H2, but a new issue will be created with low priority for shifting to mySQL

@f-fromont f-fromont added Priority: Low Something which is nice to have. and removed Priority: Medium labels Mar 11, 2022
@jessicafenwick jessicafenwick mentioned this issue Mar 11, 2022
Closed
@f-fromont f-fromont added Status: Available This issue is available for some to pick up. and removed Status: Available This issue is available for some to pick up. labels Mar 14, 2022
@f-fromont
Copy link
Contributor Author

Closing issue, as a current method is working, and changing database implementations could be better defined in a new issue for future team

Project automation moved this from To do to Done Mar 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@f-fromont f-fromont

Labels
Priority: Low Something which is nice to have. Status: Available This issue is available for some to pick up. Type: Maintenance The issue is about maintenance which doesn't change the functionality of the code, e.g. refactoring
Projects
Project
Done
Milestone
No milestone
Development

No branches or pull requests
1 participant
@f-fromont