-
Notifications
You must be signed in to change notification settings - Fork 155
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
docs: fix grammar #135
docs: fix grammar #135
Conversation
++
documentation/crud/cursors.md:
is it correct sentence?
How about to replace it with "Get description of the last error"? documentation/conf/scheduler.md: |
+++ sp_setstring(): What does if it is 0, it calculates string size by if it is a size of string, then why is there such code:
there should be Probably zero keys are bad idea. This is done mostly to simplify configuration. By default all fields are not initialized (unset). So basically, if we zero values we should not set them. This might be confusing. Yes. You right about example, yet it will work if every key will be zero terminated in the example. |
++
Yes, that is incorrect. It should be 600 at least or 0. Snapshots are turned off in upcoming v2.2 by default. documentation/crud/cursors.md:
is it correct sentence? Second and futher sp_get() calls must use previously allocated result object to continue iteration.
How about to replace it with "Get description of the last error"? documentation/conf/scheduler.md: It is mostly semantical. We can do sp_setstring() (or getstring) on function type field and expect that it will be executed. |
++++ |
++++ This mostly made for simplicity, eg. FFI support. |
Thank you. |
No description provided.