Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upCan't implement InternalSaveChangesDsl for another backend #1736
Comments
weiznich
added
hole in api
accepted
internal or unreleased api
labels
May 28, 2018
This comment has been minimized.
|
This isn't really a bug in Diesel, but more a limitation of the language. To fix this we would need disjointness based on associated types, and probably specialization as well. Without those in the language, there's nothing we can do about this. The orphan rules exist for a reason. |
sgrif
closed this
May 29, 2018
This comment has been minimized.
|
@weiznich Has an idea about how to fix this. |
sgrif
reopened this
May 29, 2018
added a commit
to GiGainfosystems/diesel
that referenced
this issue
May 30, 2018
added a commit
to weiznich/diesel
that referenced
this issue
Jun 7, 2018
weiznich
closed this
in
#1741
Jun 15, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
pgab commentedMay 28, 2018
•
edited by weiznich
Setup
Versions
Problem Description
I am trying to get another backend for diesel working. Namely oracle/oci. Therefore I need to implement e.g.
InternalSaveChangesDsl. Since all oracle/oci related code is currently outside of diesel, it is impossible to implement this. Please note that I madesave_changes_dslpublic.What is the actual output?
Steps to reproduce
There is some code at https://github.com/GiGainfosystems/diesel-oci/tree/feature/save_changes_dsl available. I also had to change some diesel code: https://github.com/GiGainfosystems/diesel/tree/feature/save_changes_dsl
Within
diesel/diesel_testsI runChecklist
closed if this is not the case)