-
-
Notifications
You must be signed in to change notification settings - Fork 195
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
fix type and precision for unix_timestamp
#2576
Conversation
Additional work is required for integration with Dolt. |
3 similar comments
Additional work is required for integration with Dolt. |
Additional work is required for integration with Dolt. |
Additional work is required for integration with Dolt. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, good set of new tests
@@ -456,7 +543,10 @@ func (ut *UnixTimestamp) IsNullable() bool { | |||
} | |||
|
|||
func (ut *UnixTimestamp) Type() sql.Type { | |||
return types.Float64 | |||
if ut.typ == nil { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can type be nil? with the constructor changes?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The changes do add either Int64
or Float64
, but I don't think it's impossible for type to the nil
.
The check will prevent panics.
builds off of: #2573