chr function returns one character from the ascii code argument.
SUCCESS: Integrated in Tajo-trunk-postcommit #608 (See https://builds.apache.org/job/Tajo-trunk-postcommit/608/)
TAJO-307: Implement chr(int) function. (DaeMyung Kang via hyunsik) (hyunsik: https://git-wip-us.apache.org/repos/asf?p=incubator-tajo.git&a=commit&h=ad6ff6ede187bea29e64c1745fad4d90f7049433)
committed it to master. Thanks!
PostgreSQL String function manual describes that chr() can take UTF8 code point. However, in this time, the given range limit may be proper. When needed, we would expand the range limit.
Please review this.
It's operations is somewhat different from posgresql's
I just limit it's bound from 1 to 65525(Unicode UCS2 range)
but postgresql allow to input until 2097151(but it just returns "")
so I need some advice.
Should we make this function like postgresql's?
Because you are already a contributor, you can assign issues to yourself.
I assigned to you.
I'd like to solve this issue. please assign to me