Francesco Capponi

Hi @penghuo, The system is for sure many features but it has several challenges when trying to use and extend. It abstract away and compounds authentication, authorization and masking into...

Also this I believe it's a breaking change

@dai-chen Shouldn't it fall back to the old one automatically when the query throws? If not, could we enable that fallback somehow?

> > @dai-chen Shouldn't it fall back to the old one automatically when the query throws? > > If not, could we enable that fallback somehow? > > Yes, fall...

As additional data point, another valid format in Postgres is `20181231` (opposed to `2018-12-31`)

As fix you can use this branch @gauravlanjekar https://github.com/FreCap/sql/tree/nestedLimit-comparison-datecast You can find the build here: https://github.com/FreCap/sql/actions/runs/1053174786

Thanks @dai-chen and @penghuo. IMO handling it like Postgres is probably ideal for most users since it is a less strict behavior but still well recognized.

`Yeah, we'll do some evaluation. ` Great. Yes, I have integrations with BI tools (unfortunately cannot disclose further).

Thank you for the poitner! Is there any reason why we should keep it that way and not a large number? It's completely opaque from the user perspective

@penghuo would you have any suggestion/internal agreement on changing the default value or how to make this parametric? Any preference in making this parametric between: 1) static config in yml...