normanj-bitquill

@MaxKsyunz Thank you for the update. Do you know if the OpenSearch JDBC Driver is vulnerable to this CVE?

I'd like to add to this. Some applications will make use of multiple AWS access keys, so the environment variables are not really a solution. This line is forcing property...

In order to separate the POWER function for PostgreSQL and non-PostgreSQL dialects, the POWER function was moved to the `SqlLibraryOperators` class. This downgrades the POWER function from a standard function...

Need to properly separate the MySQL/Oracle implementation of `TO_CHAR` from the PostgreSQL implementation.

@mihaibudiu > The amount of testing is very impressive. These won't be easy to review. I assume they were checked against postgres. You should address the failures reported by the...

@caicancai > I remember that calcite currently has support for the postgres to_char function. Should we remove the previous support? The existing TO_CHAR function is used by MySQL and Oracle,...

@mihaibudiu > Until https://issues.apache.org/jira/browse/CALCITE-6281 has a solution, the best way to test this may be to create a Quidem test file (.iq suffix). If that file is identical with the...

@mihaibudiu Here is the output of a PostgreSQL script running all of the `TO_CHAR` tests from the `postgresql.iq` file in this PR. I kept the expected output for Calcite in...

@mihaibudiu > This is pretty close, the existing file `core/src/test/resources/sql/sub-query.iq` already uses the postgres format. What I would do is to make a small python script to convert the postgres...

> I don't understand why the CI fails. Can you please rebase on main? Maybe it has something to do with the recent transition to 1.37 which had some build...