Audit names of PyDough operators to potentially standardize some of them #204
Labels
documentation
Improvements or additions to documentation
effort - low
quick & simple issue
refactor
improving the quality of PyDough code
user feature
Adding a new user-facing feature/functionality
The names of PyDough operators can vary between being Pythonic, SQL-esque, or rooted in a phrasing that would be used in the text for an analytical question. Goal of this issue is to go through all the operator names and decide if any should be changed (in any of those 3 directions). Examples:
PRESENT
/ABSENT
is textual (could beNOTNA
/ISNA
which is pythonic, orIS_NOT_NULL
/IS_NULL
which is SQL-esuqe)JOIN_STRINGS
is Pythonic (could beCONCAT_WS
which is SQL-esque)DEFAULT_TO
is textual (could beCOALESCE
which is SQL-esuqe, orFILLNA
which is Pythonic)LIKE
is SQL-esuqe (could beMATCHES_PATTERN
which is textual)ISIN
is Pythonic (could beIN
which is more SQL-esque orCONTAINED_BY
which is more textual)ABS
is SQL-esque/Pythonic (could beABSOLUTE_VALUE
which is more textual)MONOTONIC
is Pythonic (could beBETWEEN
which is SQL-esque, orASCENDING
which is more textual)'KEEP_IF
is textual (could beNULL_UNLESS
which is closer to SQL-esque, orMASK
which is more Pythonic)The text was updated successfully, but these errors were encountered: