You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@calcite.apache.org by "Julian Hyde (Jira)" <ji...@apache.org> on 2019/08/19 19:04:00 UTC

[jira] [Commented] (CALCITE-3263) Add MD5, SHA1 SQL functions

    [ https://issues.apache.org/jira/browse/CALCITE-3263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16910662#comment-16910662 ] 

Julian Hyde commented on CALCITE-3263:
--------------------------------------

Please rename the test methods from "testMD5" to "testMd5". We initialize acronyms.

There is not exactly consensus on these functions. BigQuery, example, accepts both string and binary as arguments, and returns a BINARY. Oracle has STANDARD_HASH and returns a RAW value. Is Redshift consistent with PostgreSQL? Please add to this Jira case a review of what other databases do. It will be a template for future work.

 

> Add MD5, SHA1 SQL functions
> ---------------------------
>
>                 Key: CALCITE-3263
>                 URL: https://issues.apache.org/jira/browse/CALCITE-3263
>             Project: Calcite
>          Issue Type: Improvement
>            Reporter: ShuMing Li
>            Priority: Minor
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> `MD5/SHA1` functions are common UDFs in many SQL engines. We may support them in SQL just like `from_base64`/`to_base64`.
>  
> - MySQL: https://dev.mysql.com/doc/refman/8.0/en/encryption-functions.html
> - PostgreSQL: https://www.postgresql.org/docs/current/functions-string.html



--
This message was sent by Atlassian Jira
(v8.3.2#803003)