Re: [DISCUSS] String literal behavior in Flink

2023-03-07 Thread Jark Wu
Thank you for sharing this good news! I think we can create an issue for upgrading to Calcite 1.33 and mention the waiting feature. Best, Jark > 2023年3月6日 22:16,Aitozi 写道: > > Hi, Jark > >FYI, this feature has already been supported in Calcite 1.33.0 [1]. > Therefore, I believe we c

Re: [DISCUSS] String literal behavior in Flink

2023-03-06 Thread Aitozi
Hi, Jark FYI, this feature has already been supported in Calcite 1.33.0 [1]. Therefore, I believe we can use it directly after upgrading the Calcite version. Best, Aitozi. [1]: https://issues.apache.org/jira/browse/CALCITE-5305 Aitozi 于2023年3月6日周一 16:48写道: > Thanks, will give it a try > >

Re: [DISCUSS] String literal behavior in Flink

2023-03-06 Thread Aitozi
Thanks, will give it a try Best, Aitozi. Jark Wu 于2023年3月6日周一 15:11写道: > Hi Aitozi, > > I would suggest trying to contribute it to the upstream project Calcite > first. > > Best, > Jark > > > 2023年3月6日 11:51,Aitozi 写道: > > > > Hi Jark, > > > > Thank you for your helpful suggestion. It appears

Re: [DISCUSS] String literal behavior in Flink

2023-03-05 Thread Jark Wu
Hi Aitozi, I would suggest trying to contribute it to the upstream project Calcite first. Best, Jark > 2023年3月6日 11:51,Aitozi 写道: > > Hi Jark, > > Thank you for your helpful suggestion. It appears that 'E'foo\n'' is a more > versatile and widely accepted option. To assess its feasibility, I

Re: [DISCUSS] String literal behavior in Flink

2023-03-05 Thread Aitozi
Hi Jark, Thank you for your helpful suggestion. It appears that 'E'foo\n'' is a more versatile and widely accepted option. To assess its feasibility, I have reviewed the relevant Unicode supports and concluded that it may necessitate modifications to the Parser.jj file to accommodate this new synt

Re: [DISCUSS] String literal behavior in Flink

2023-03-05 Thread Jark Wu
Hi Aitozi, I think this is a good idea to improve the backslash escape strings. However, I lean a bit more toward the Postgres approach[1], which is more standard-compliant. PG allows backslash escape string by writing the letter E (upper or lower case) just before the opening single quote, e.g.,