Hi Rui,
Thanks for your reply.
I also prefer [long + TimeZone] as internal representation of TIMESTAMP
WITH TIME ZONE, and
[int + TimeZone] as representation of TIME WITH TIME ZONE for the following
reasons:
1) Current Calcite codebase use java.sql.TimeZone to describe time zone
information(as
Thanks Gelbana,
Very appreciated your explanation, which sheds me some light on exploring
Calcite. :)
Best wishes,
Trista
Juan Pan (Trista)
Senior DBA & PPMC of Apache ShardingSphere(Incubating)
E-mail: panj...@apache.org
On 12/22/2019 05:58，Muhammad Gelbana
Vladimir Sitnikov created CALCITE-3623:
--
Summary: Replace Spotless with Autostyle
Key: CALCITE-3623
URL: https://issues.apache.org/jira/browse/CALCITE-3623
Project: Calcite
Issue Type:
Forward Xu created CALCITE-3622:
---
Summary: Update geode tests upgrade from junit4 to junit5
Key: CALCITE-3622
URL: https://issues.apache.org/jira/browse/CALCITE-3622
Project: Calcite
Issue
Here are my availability times in case we won't use doodle. Do you think
it's useful to record and save those meetings ?
Mohamed
==
Option 1: Sun-Thur 15:00-19:0
Option 2: Fri 12:00-19:00
Option 3: Sat 10:00 AM - 12:00
On Sun, Dec 22, 2019 at 12:12 AM Muhammad Gelbana
wrote:
> I love the
