-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
int32 #55
Comments
Thanks a lot for the quick response! |
Sorry I don't understand. What you mean? |
sqlite3_bind_int returns a 32-bit value both on 32-bit and 64-bit machine. The current code is okay for 32-bit machines, but suppose we're working on amd64. Here, when a Go integer is read, sqlite3_bind_int is called. Go integers are 64-bit on amd (well, will be, starting from go 1.1), so I think the correct behavior is to call sqlite3_bind_int64 instead of sqlite3_bind_int on the next line. Does this make sense? |
Ah, I understand just now. Thank you. |
Fixed it. |
Thanks a bunch! |
Is there any particular reason why int32 data type is not supported?
Also, I don't think executing sqlite3_bind_int for go's int type is the correct action in general. On amd64, C int's are usually 32-bit whereas go ints are 64-bit.
The text was updated successfully, but these errors were encountered: