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
Readme Select: Cols vs Set functionality is unclear #14
Comments
|
@jakeasmith would love to get a PR. Thanks. |
|
I don't have time right now, but I wanted to at least open up the issue here. Its tripped my team up more than once. |
|
@jakeasmith sure. I just mentioned. |
|
@jakeasmith I am not sure whether moving to |
|
I just modified the read me very slightly. Let me know if that helps. Regarding the phrase "its not obvious that set() is its own key-value pair unrelated to cols() and bind*()" -- I don't think it's unrelated. The set() method is a raw connection to the column/value pairs. You could mimic cols()+bind() by calling set() multiple times and passing your own values. |
|
I think the biggest thing that wasn't clear to me, was that you can use set() OR cols() OR both, partly because the example shows them used all together. So showing them in separate examples is one way that could help explain the usage. |
|
/me nods I'm not sure how to write that up -- if you could send a PR that would help a great deal. |
|
Guys, I'm sorry, I don't know how to write this up any better. If you can send a PR with better examples I'll be happy to review it. In the mean time, I'm closing this issue; I can reopen it or reference it later as needed. |
|
may be we close it once they feel it is addressed ? I know our release script probably won't allow for it :( . |
From this example its not obvious that
set()is its own key-value pair unrelated tocols()andbind*(). Consider splittingset()into its own example.The text was updated successfully, but these errors were encountered: