Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upShow usage of `sql_query` on the homepage #62
Merged
Conversation
On Reddit it was recently mentioned that `sql_query` felt like a second class API. That was never the intention, and I think it's worth promoting here. Either way, I think that `sql_query` and `#[derive(QueryableByName)]` is much easier to use than the alternatives, even if that's the only part of Diesel you actually use. We should promote it as such.
This comment has been minimized.
This comment has been minimized.
dcarosone
commented
May 25, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.



sgrif commentedMay 23, 2018
On Reddit it was recently mentioned that
sql_queryfelt like a secondclass API. That was never the intention, and I think it's worth
promoting here.
Either way, I think that
sql_queryand#[derive(QueryableByName)]ismuch easier to use than the alternatives, even if that's the only part
of Diesel you actually use. We should promote it as such.