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.

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

Switch to PostgreSQL #11

Closed
ineshbose opened this issue Nov 7, 2021 · 3 comments · Fixed by #122
Closed

Switch to PostgreSQL #11

ineshbose opened this issue Nov 7, 2021 · 3 comments · Fixed by #122
Assignees
Labels
enhancement New feature or request

Comments

@ineshbose
Copy link
Owner

Is your feature request related to a problem?

Provide a clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Currently and by default, Django uses SQLite to keep a database which is also just file based. The most preferred and robust system for Django is PostgreSQL.

Describe the solution you'd like

Please provide a clear and concise description of what you want to happen.

Change values in settings.py to switch to PostgreSQL.

Describe alternatives you've considered

Please provide a clear and concise description of any alternative solutions or features you've considered.

Other databases like MySQL, MongoDB, etc.

@ineshbose ineshbose added the enhancement New feature or request label Nov 7, 2021
@ineshbose
Copy link
Owner Author

This would be best to implement once the models themselves are also in place since it's easier to reset database with SQLite (just by deleting db.sqlite3). With that said, that also means to avoid using PostgreSQL special fields like ArrayField and just ManyToMany or ManyToOne.

@ineshbose
Copy link
Owner Author

/cib

@github-actions
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant