-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Use postgresql database #87
Comments
It's definitely possible - diesel that's used as ORM layer does support Postgres, however it's not an easy task to do that. Having DB backed swap-able in place is not goal of diesel and hence you need some work around this. Having said that I don't think we use SQL directly outside of the migrations code, so if someone is motivated enough to dive into the code to do that, patches would be welcome. |
Note that we're using replace_into a lot. It appears, that this might not be supported with Postgres. |
Upserts were added in 9.5, so this is supported on version 9.5 and up. Not looked at the bw_rs code to see how much work it would be yet. |
It would be very helpful tonbe able to deploy bw_rs in Kubernetes and ease the backup of the files! Also running multiple nodes without direct file sharing |
To keep the issue tracker more focused, I'm closing this issue in favor of the meta issue at #246. |
…ioned in dani-garcia#246. This includes migrations as well as Dockerfile's for amd64. The biggest change is that replace_into isn't supported by Diesel for the PostgreSQL backend, instead requiring the use of on_conflict. This unfortunately requires a branch for save() on all of the models currently using replace_into.
Adds support for PostgreSQL which adds dani-garcia#87 and is mentioned in dani-garcia#246.
Hi! Would it be possible to add support for PostgreSQL? I'd like to use a database independent of the docker container.
The text was updated successfully, but these errors were encountered: