Thanks & will do.
Having tested the trunk /pending release changes, they resolved the issue
we had been seeing.
Andrew
On Fri, 7 Jun 2019, 20:53 Julian Hyde, wrote:
> If you encounter further issues, please log them. We can’t fix them if we
> don’t know what they are. (We won’t necessarily
If you encounter further issues, please log them. We can’t fix them if we don’t
know what they are. (We won’t necessarily fix them… we’re busy too… but they
might be easy to fix while we’re fixing something else.)
With Babel, due to its very large scope, there are a lot of unknown issues.
Thanks for the replies.
@Yuzhao unfortunately I won't be able to change the input sql to add the
quotes, so as you point out the UDF may have issues with the reserved
word.
@Hongze, Yes, I'm only interested in parsing. I had tried the Babel parser
without success (on v1.19.0). However that's
Another choice is just like you said, you can add Date as UDF but because
Date is a reserved word, you may need to quote the function name like
`Date`(col1) based on what quoting character you use.
Andrew O 于2019年6月6日周四 下午7:07写道：
> I'm doing a project trying to parse some IBM DB2 sql
Hi Andrew,
If you are focusing parsing only, I believe you can just use the babel parser -
in babel we have added support for DATE function via CALCITE-3022. The thing is
you need to compile Calcite's code by yourself - 1.20.0 hasn't been released
yet.
Hongze
> On Jun 6, 2019, at 19:06,
I'm doing a project trying to parse some IBM DB2 sql expressions (to
analyze table / column usages).
To note,
1) these are existing ad-hoc user queries so I can't change their syntax
2) I don't have a connection / schema for the database, but my
understanding is that this shouldn't be required
