We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
iter := query.Iter(conn) if iter.Error() != nil { log.Panicln(iter.Error()) }
I think it would be better that iter use muti-return val, which is golang API usually do.
iter, err := query.Iter(conn) if err != nil { log.Panicln(err) }
The text was updated successfully, but these errors were encountered:
@m1nor How do u think about it?
Sorry, something went wrong.
The correct example is in README
for iter.Scan(&name, &date) { // } if iter.Error() != nil { log.Panicln(iter.Error()) }
Errors in Scan will also be accessible via iter.Error(). I don't think we should break compatibility to separate Iter creation errors and Scan errors.
I'm not closing this issue because it really should be discussed.
No branches or pull requests
I think it would be better that iter use muti-return val, which is golang API usually do.
The text was updated successfully, but these errors were encountered: