You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I would like to be able to express integer constants in hexadecimal. Our database has bit flag columns (sigh) and so working with hex constants is best in this case.
Example:
SELECT
b.flag_column & 0x08 != 0 AS my_special_flag, -- FLAG_MY_SPECIAL_FLAG
It would be nice if RisingWave could support all the above latest PG 16 syntax.
Describe alternatives you've considered
The workaround seems to be to express the numbers in decimal. However, the flag values are harder to read in such a case, and also don't align well with the original PHP code which expresses the constants using hexadecimal.
So it hurts readability in our case.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I would like to be able to express integer constants in hexadecimal. Our database has bit flag columns (sigh) and so working with hex constants is best in this case.
Example:
Describe the solution you'd like
PG 16 added support for non-decimal numeric constants, like decimal numbers: https://www.postgresql.org/docs/16/sql-syntax-lexical.html#SQL-SYNTAX-CONSTANTS-NUMERIC
All are valid examples in binary, octal, and hex, from the docs:
Also you are allowed to add some "comma separators" to the numbers using underscores for readability:
It would be nice if RisingWave could support all the above latest PG 16 syntax.
Describe alternatives you've considered
The workaround seems to be to express the numbers in decimal. However, the flag values are harder to read in such a case, and also don't align well with the original PHP code which expresses the constants using hexadecimal.
So it hurts readability in our case.
Additional context
No response
The text was updated successfully, but these errors were encountered: