-
Notifications
You must be signed in to change notification settings - Fork 28
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
Assert failure retreiving a TIMESTAMP value #9
Comments
|
It seems that TIMESTAMP values have the "unsigned" flag set, unlike DATETIME and other non-numeric types. Unfortunately, I can't find any documentation regarding the intended behavior of the unsigned flag on non-numeric types. So I don't know why this is, or whether or not it's always the case. However, the MySQL protocol's documentation does state that TIMESTAMP's actual value information (aside from the flags) is exactly the same as DATETIME. So, ignoring the "unsigned" flag should work fine. And indeed it does seem to work fine for both me and at least one other user. In any case, the triggered assertion turned out be faulty anyway: It erroneously assumed that non-integer types cannot be unsigned. This was a false assumption: Not only does TIMESTAMP (apparently) report itself as unsigned, but MySQL also permits floating-point and fixed-point types to be unsigned. |
|
Fixed by commit 93361e7 |
|
There is a similar assert within the method |
|
Fixed by commit a8a3827 |
Retrieving a TIMESTAMP value causes an assert to fail at location
mysql/connection.d(1046).I'm still investigating this further...
The text was updated successfully, but these errors were encountered: