Skip to content
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

Merged
merged 21 commits into from
Jul 1, 2024
Merged

fix type and precision for unix_timestamp #2576

merged 21 commits into from
Jul 1, 2024

Conversation

jycor
Copy link
Contributor

@jycor jycor commented Jun 28, 2024

builds off of: #2573

Copy link

Additional work is required for integration with Dolt.

3 similar comments
Copy link

Additional work is required for integration with Dolt.

Copy link

Additional work is required for integration with Dolt.

Copy link

Additional work is required for integration with Dolt.

Copy link
Contributor

@max-hoffman max-hoffman left a 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 {
Copy link
Contributor

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?

Copy link
Contributor Author

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.

@jycor jycor merged commit 77fa279 into main Jul 1, 2024
8 checks passed
@jycor jycor deleted the james/unix branch July 1, 2024 18:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants