Thanks for your help on this topic, Qianjin! It would be great if you are
willing to contribute more. Be free to file JIRA issues / open PRs at the time
when you think is right.
Best,
Hongze
Hongze
From: ForwardXu
Date: 2019-02-25 09:43
To: Hongze Zhang
Subject: Integrating MySQL's JSON
Forward Xu created CALCITE-2864:
---
Summary: Add the JSON_DEPTH function
Key: CALCITE-2864
URL: https://issues.apache.org/jira/browse/CALCITE-2864
Project: Calcite
Issue Type: New Feature
Hi Honeze Zhang,
Thank you very much for the late review and merge the PR for JSON_TYPE. I think
JSON_TYPE has completed the first step of the whole Mysql JSON function. I
think we can continue the JSON_DEPTH/JSON_LENGTH functions.
best
qianjin
We did this in the project that I am currently working on but this part is
not open source so I don't have a link to give you.
Στις Σάβ, 23 Φεβ 2019 στις 9:35 μ.μ., ο/η Andrei Sereda
έγραψε:
> > There are two tricky (but doable) parts:
> > 1) pass bound variables from one convention to the
zabetak commented on a change in pull request #950: [CALCITE-2703] Reduce code
generation and class loading overhead when executing queries in the
EnumerableConvention (Stamatis Zampetakis)
URL: https://github.com/apache/calcite/pull/950#discussion_r259641994
##
File path:
MGelbana opened a new pull request #1066: [CALCITE-2843] Babel parser should
support PostgreSQL casting operator '::'
URL: https://github.com/apache/calcite/pull/1066
Initial support for PostgreSQL OID types (oid, regproc, repoper..etc) is
also included in the form of two test cases and
