Open XiaochenCui opened 1 month ago
Hello, I am Blathers. I am here to help you get the issue triaged.
It looks like you have not filled out the issue in the format of any of our templates. To best assist you, we advise you to use one of these templates.
I have CC'd a few people who may be able to assist you:
If we have not gotten back to your issue within a few business days, you can try the following:
:owl: Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.
Should I edit this issue to fit the format of the template?
Should I edit this issue to fit the format of the template?
No need, thanks
@rytaft This seems more like sql-queries change or is there something specific we need on the foundations side to support this (i.e. related to the type or something else)?
hi @fqazi
this issue is legit but it may be hard to implement, "TIME" data type may not have extra space to store special values (especially for values outside [00:00:00 - 24:00:00]) (I'm not sure about that and going to verify it later)
This felt to me like a SQL Foundations issue since it is related to the TIME datatype. But I agree that the line here is fuzzy. I'll add it to our project as well.
Ah that makes more sense, and definitely has foundations aspects then. Thank you @rytaft @XiaochenCui
In the current implementation,
'infinity'::time
is equal to'23:59:59.999999'
and smaller than'24:00:00'
. We should make it greater than any other time to fit the semantics of 'infinity', and the updated behaviour will also aligne with pr https://github.com/cockroachdb/cockroach/pull/127141Alternatively, we can align it's behaviour with postgres, which prohibits
'infinity'::time
:This issue complements issue https://github.com/cockroachdb/cockroach/issues/41564
Jira issue: CRDB-41399