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

COALESCE failing for NULL timestamps #4478

Closed
1 task done
javier opened this issue May 7, 2024 · 0 comments · Fixed by #4490
Closed
1 task done

COALESCE failing for NULL timestamps #4478

javier opened this issue May 7, 2024 · 0 comments · Fixed by #4490
Labels
Bug Incorrect or unexpected behavior

Comments

@javier
Copy link
Contributor

javier commented May 7, 2024

To reproduce

select
      coalesce(null :: timestamp, 1),
      coalesce(null, 1),
      coalesce(now(), 1),
      coalesce(null, null :: timestamp)

The first two coalesce statements should return 1, but the first one returns the incorrect value of 1970-01-01T00:00:00.000001Z. The other two coalesce statements are there just to show with non-null values, or when the null::timestamp is used as a return value it all works as expected.

Maybe related to this issue

QuestDB version:

7.4.3

OS, in case of Docker specify Docker and the Host OS:

OSx

File System, in case of Docker specify Host File System:

ext4

Full Name:

javier ramirez

Affiliation:

questdb

Have you followed Linux, MacOs kernel configuration steps to increase Maximum open files and Maximum virtual memory areas limit?

  • Yes, I have

Additional context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Incorrect or unexpected behavior
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant