julianhyde commented on code in PR #3338: URL: https://github.com/apache/calcite/pull/3338#discussion_r1291828491
########## site/_docs/reference.md: ########## @@ -2776,6 +2776,7 @@ BigQuery's type system uses confusingly different names for types and functions: | b | PARSE_TIMESTAMP(format, string[, timeZone]) | Uses format specified by *format* to convert *string* representation of timestamp to a TIMESTAMP WITH LOCAL TIME ZONE value in *timeZone* | h s | PARSE_URL(urlString, partToExtract [, keyToExtract] ) | Returns the specified *partToExtract* from the *urlString*. Valid values for *partToExtract* include HOST, PATH, QUERY, REF, PROTOCOL, AUTHORITY, FILE, and USERINFO. *keyToExtract* specifies which query to extract | b | POW(numeric1, numeric2) | Returns *numeric1* raised to the power *numeric2* +| b | REGEXP_CONTAINS(value, regexp) | Returns TRUE if *value* is a partial match for the regular expression, *regexp* Review Comment: I understand your dilemma. I think it's better to make the Calcite descriptions uniform, even if they come from many different DBs. In `big-query.iq`, feel free to use the doc copy-pasted from BigQuery. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
