Is your feature request related to a problem?

any query WHERE ts IN '$now-10_000T..$now-9_900T' fails with Unexpected characters after unit, but we have elsewhere that we can use the underscore separator for config values, so I was wondering if we should accept it here as well?

Describe the solution you'd like.

No response

Describe alternatives you've considered.

No response

Full Name:

javier

Affiliation:

questdb

Additional context

No response