commits  

Messages by Thread

• • Re: [PR] [CALCITE-7359] Incorrect result for array comparison with ANY operator [calcite] via GitHub
  • Re: [PR] [CALCITE-7359] Incorrect result for array comparison with ANY operator [calcite] via GitHub
  • Re: [PR] [CALCITE-7359] Incorrect result for array comparison with ANY operator [calcite] via GitHub
  • Re: [PR] [CALCITE-7359] Incorrect result for array comparison with ANY operator [calcite] via GitHub
  • Re: [PR] [CALCITE-7359] Incorrect result for array comparison with ANY operator [calcite] via GitHub
  • Re: [PR] [CALCITE-7359] Incorrect result for array comparison with ANY operator [calcite] via GitHub
  • Re: [PR] [CALCITE-7359] Incorrect result for array comparison with ANY operator [calcite] via GitHub
  • Re: [PR] [CALCITE-7359] Incorrect result for array comparison with ANY operator [calcite] via GitHub
  • Re: [PR] [CALCITE-7359] Incorrect result for array comparison with ANY operator [calcite] via GitHub
  • Re: [PR] [CALCITE-7359] Incorrect result for array comparison with ANY operator [calcite] via GitHub
  • Re: [PR] [CALCITE-7359] Incorrect result for array comparison with ANY operator [calcite] via GitHub
  • Re: [PR] [CALCITE-7359] Incorrect result for array comparison with ANY operator [calcite] via GitHub
  • Re: [PR] [CALCITE-7359] Incorrect result for array comparison with ANY operator [calcite] via GitHub
  • Re: [PR] [CALCITE-7359] Incorrect result for array comparison with ANY operator [calcite] via GitHub
  • Re: [PR] [CALCITE-7359] Incorrect result for array comparison with ANY operator [calcite] via GitHub
  • Re: [PR] [CALCITE-7359] Incorrect result for array comparison with ANY operator [calcite] via GitHub
  • Re: [PR] [CALCITE-7359] Incorrect result for array comparison with ANY operator [calcite] via GitHub
  • Re: [PR] [CALCITE-7359] Incorrect result for array comparison with ANY operator [calcite] via GitHub
  • Re: [PR] [CALCITE-7359] Incorrect result for array comparison with ANY operator [calcite] via GitHub
  • Re: [PR] [CALCITE-7359] Incorrect result for array comparison with ANY operator [calcite] via GitHub
  • Re: [PR] [CALCITE-7359] Incorrect result for array comparison with ANY operator [calcite] via GitHub
  • Re: [PR] [CALCITE-7359] Incorrect result for array comparison with ANY operator [calcite] via GitHub
  • Re: [PR] [CALCITE-7359] Incorrect result for array comparison with ANY operator [calcite] via GitHub
  • Re: [PR] [CALCITE-7359] Incorrect result for array comparison with ANY operator [calcite] via GitHub
  • Re: [PR] [CALCITE-7359] Incorrect result for array comparison with ANY operator [calcite] via GitHub
  • Re: [PR] [CALCITE-7359] Incorrect result for array comparison with ANY operator [calcite] via GitHub
  • Re: [PR] [CALCITE-7359] Incorrect result for array comparison with ANY operator [calcite] via GitHub
  • Re: [PR] [CALCITE-7359] Incorrect result for array comparison with ANY operator [calcite] via GitHub
  • Re: [PR] [CALCITE-7359] Incorrect result for array comparison with ANY operator [calcite] via GitHub
  • Re: [PR] [CALCITE-7359] Incorrect result for array comparison with ANY operator [calcite] via GitHub
• (calcite) branch main updated (ab6a397c91 -> c0d5a08328) xiong
• (calcite-site) branch main updated: Website deployed from calcite@ab6a397c9161824ef00715fba41eef54a39a083d asf-ci-deploy
• (calcite) branch site updated: [CALCITE-7301] Add common test for SqlNode unparse after deep copy and missing createCall in operators github-bot
• (calcite) branch main updated: [CALCITE-7301] Add common test for SqlNode unparse after deep copy and missing createCall in operators dmsysolyatin
• Re: [PR] [CALCITE-7301] Add common test for SqlNode unparse after deep copy and missing createCall in operators [calcite] via GitHub
• (calcite) branch main updated: [CALCITE-7355] RelToSqlConverter throws exception when the join condition contains a correlated subquery xiong
• [PR] [CALCITE-7358] Casts involving MAP and ROW types cause compile-time exceptions [calcite] via GitHub
  • Re: [PR] [CALCITE-7358] Casts involving MAP and ROW types cause compile-time exceptions [calcite] via GitHub
  • Re: [PR] [CALCITE-7358] Casts involving MAP and ROW types cause compile-time exceptions [calcite] via GitHub
  • Re: [PR] [CALCITE-7358] Casts involving MAP and ROW types cause compile-time exceptions [calcite] via GitHub
  • Re: [PR] [CALCITE-7358] Casts involving MAP and ROW types cause compile-time exceptions [calcite] via GitHub
  • Re: [PR] [CALCITE-7358] Casts involving MAP and ROW types cause compile-time exceptions [calcite] via GitHub
  • Re: [PR] [CALCITE-7358] Casts involving MAP and ROW types cause compile-time exceptions [calcite] via GitHub
  • Re: [PR] [CALCITE-7358] Casts involving MAP and ROW types cause compile-time exceptions [calcite] via GitHub
  • Re: [PR] [CALCITE-7358] Casts involving MAP and ROW types cause compile-time exceptions [calcite] via GitHub
  • Re: [PR] [CALCITE-7358] Casts involving MAP and ROW types cause compile-time exceptions [calcite] via GitHub
  • Re: [PR] [CALCITE-7358] Casts involving MAP and ROW types cause compile-time exceptions [calcite] via GitHub
  • Re: [PR] [CALCITE-7358] Casts involving MAP and ROW types cause compile-time exceptions [calcite] via GitHub
• (calcite) branch main updated: [CALCITE-5093] Quantified comparison operators (e.g. ANY) should support ARRAY arguments zhenchen
• [PR] Open join quidem test [calcite] via GitHub
  • Re: [PR] Open join quidem test [calcite] via GitHub
  • Re: [PR] Open join quidem test [calcite] via GitHub
  • Re: [PR] Open join quidem test [calcite] via GitHub
  • Re: [PR] Open join quidem test [calcite] via GitHub
  • Re: [PR] Open join quidem test [calcite] via GitHub
• [PR] [CALCITE-7357] Introduce the implementation of rex operator IS DISTINCT FROM [calcite] via GitHub
  • Re: [PR] [CALCITE-7357] Introduce the implementation of rex operator IS DISTINCT FROM [calcite] via GitHub
  • Re: [PR] [CALCITE-7357] Introduce the implementation of rex operator IS DISTINCT FROM [calcite] via GitHub
  • Re: [PR] [CALCITE-7357] Introduce the implementation of rex operator IS DISTINCT FROM [calcite] via GitHub
  • Re: [PR] [CALCITE-7357] Introduce the implementation of rex operator IS DISTINCT FROM [calcite] via GitHub
  • Re: [PR] [CALCITE-7357] Introduce the implementation of rex operator IS DISTINCT FROM [calcite] via GitHub
  • Re: [PR] [CALCITE-7357] Introduce the implementation of rex operator IS DISTINCT FROM [calcite] via GitHub
  • Re: [PR] [CALCITE-7357] Introduce the implementation of rex operator IS DISTINCT FROM [calcite] via GitHub
  • Re: [PR] [CALCITE-7357] Introduce the implementation of rex operator IS DISTINCT FROM [calcite] via GitHub
  • Re: [PR] [CALCITE-7357] Introduce the implementation of rex operator IS DISTINCT FROM [calcite] via GitHub
  • Re: [PR] [CALCITE-7357] Introduce the implementation of rex operator IS DISTINCT FROM [calcite] via GitHub
  • Re: [PR] [CALCITE-7357] Introduce the implementation of rex operator IS DISTINCT FROM [calcite] via GitHub
  • Re: [PR] [CALCITE-7357] Introduce the implementation of rex operator IS DISTINCT FROM [calcite] via GitHub
  • Re: [PR] [CALCITE-7357] Introduce the implementation of rex operator IS DISTINCT FROM [calcite] via GitHub
  • Re: [PR] [CALCITE-7357] Introduce the implementation of rex operator IS DISTINCT FROM [calcite] via GitHub
  • Re: [PR] [CALCITE-7357] Introduce the implementation of rex operator IS DISTINCT FROM [calcite] via GitHub
  • Re: [PR] [CALCITE-7357] Introduce the implementation of rex operator IS DISTINCT FROM [calcite] via GitHub
• [PR] [CALCITE-7355] RelToSqlConverter throws exception when the join condi… [calcite] via GitHub
  • Re: [PR] [CALCITE-7355] RelToSqlConverter throws exception when the join condi… [calcite] via GitHub
  • Re: [PR] [CALCITE-7355] RelToSqlConverter throws exception when the join condi… [calcite] via GitHub
  • Re: [PR] [CALCITE-7355] RelToSqlConverter throws exception when the join condi… [calcite] via GitHub
  • Re: [PR] [CALCITE-7355] RelToSqlConverter throws exception when the join condi… [calcite] via GitHub
  • Re: [PR] [CALCITE-7355] RelToSqlConverter throws exception when the join condi… [calcite] via GitHub
  • Re: [PR] [CALCITE-7355] RelToSqlConverter throws exception when the join condi… [calcite] via GitHub
  • Re: [PR] [CALCITE-7355] RelToSqlConverter throws exception when the join condi… [calcite] via GitHub
  • Re: [PR] [CALCITE-7355] RelToSqlConverter throws exception when the join condi… [calcite] via GitHub
• [PR] [CALCITE-7315] Support LEFT_MARK type for hash join in enumerable convention [calcite] via GitHub
  • Re: [PR] [CALCITE-7315] Support LEFT_MARK type for hash join in enumerable convention [calcite] via GitHub
  • Re: [PR] [CALCITE-7315] Support LEFT_MARK type for hash join in enumerable convention [calcite] via GitHub
  • Re: [PR] [CALCITE-7315] Support LEFT_MARK type for hash join in enumerable convention [calcite] via GitHub
  • Re: [PR] [CALCITE-7315] Support LEFT_MARK type for hash join in enumerable convention [calcite] via GitHub
  • Re: [PR] [CALCITE-7315] Support LEFT_MARK type for hash join in enumerable convention [calcite] via GitHub
  • Re: [PR] [CALCITE-7315] Support LEFT_MARK type for hash join in enumerable convention [calcite] via GitHub
  • Re: [PR] [CALCITE-7315] Support LEFT_MARK type for hash join in enumerable convention [calcite] via GitHub
  • Re: [PR] [CALCITE-7315] Support LEFT_MARK type for hash join in enumerable convention [calcite] via GitHub
  • Re: [PR] [CALCITE-7315] Support LEFT_MARK type for hash join in enumerable convention [calcite] via GitHub
  • Re: [PR] [CALCITE-7315] Support LEFT_MARK type for hash join in enumerable convention [calcite] via GitHub
  • Re: [PR] [CALCITE-7315] Support LEFT_MARK type for hash join in enumerable convention [calcite] via GitHub
  • Re: [PR] [CALCITE-7315] Support LEFT_MARK type for hash join in enumerable convention [calcite] via GitHub
  • Re: [PR] [CALCITE-7315] Support LEFT_MARK type for hash join in enumerable convention [calcite] via GitHub
  • Re: [PR] [CALCITE-7315] Support LEFT_MARK type for hash join in enumerable convention [calcite] via GitHub
  • Re: [PR] [CALCITE-7315] Support LEFT_MARK type for hash join in enumerable convention [calcite] via GitHub
  • Re: [PR] [CALCITE-7315] Support LEFT_MARK type for hash join in enumerable convention [calcite] via GitHub
  • Re: [PR] [CALCITE-7315] Support LEFT_MARK type for hash join in enumerable convention [calcite] via GitHub
  • Re: [PR] [CALCITE-7315] Support LEFT_MARK type for hash join in enumerable convention [calcite] via GitHub
  • Re: [PR] [CALCITE-7315] Support LEFT_MARK type for hash join in enumerable convention [calcite] via GitHub
  • Re: [PR] [CALCITE-7315] Support LEFT_MARK type for hash join in enumerable convention [calcite] via GitHub
• [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
• [PR] [CALCITE-5093] Quantified comparison operators (e.g. ANY) should support ARRAY arguments [calcite] via GitHub
  • Re: [PR] [CALCITE-5093] Quantified comparison operators (e.g. ANY) should support ARRAY arguments [calcite] via GitHub
  • Re: [PR] [CALCITE-5093] Quantified comparison operators (e.g. ANY) should support ARRAY arguments [calcite] via GitHub
  • Re: [PR] [CALCITE-5093] Quantified comparison operators (e.g. ANY) should support ARRAY arguments [calcite] via GitHub
  • Re: [PR] [CALCITE-5093] Quantified comparison operators (e.g. ANY) should support ARRAY arguments [calcite] via GitHub
  • Re: [PR] [CALCITE-5093] Quantified comparison operators (e.g. ANY) should support ARRAY arguments [calcite] via GitHub
  • Re: [PR] [CALCITE-5093] Quantified comparison operators (e.g. ANY) should support ARRAY arguments [calcite] via GitHub
  • Re: [PR] [CALCITE-5093] Quantified comparison operators (e.g. ANY) should support ARRAY arguments [calcite] via GitHub
  • Re: [PR] [CALCITE-5093] Quantified comparison operators (e.g. ANY) should support ARRAY arguments [calcite] via GitHub
  • Re: [PR] [CALCITE-5093] Quantified comparison operators (e.g. ANY) should support ARRAY arguments [calcite] via GitHub
  • Re: [PR] [CALCITE-5093] Quantified comparison operators (e.g. ANY) should support ARRAY arguments [calcite] via GitHub
  • Re: [PR] [CALCITE-5093] Quantified comparison operators (e.g. ANY) should support ARRAY arguments [calcite] via GitHub
  • Re: [PR] [CALCITE-5093] Quantified comparison operators (e.g. ANY) should support ARRAY arguments [calcite] via GitHub
  • Re: [PR] [CALCITE-5093] Quantified comparison operators (e.g. ANY) should support ARRAY arguments [calcite] via GitHub
  • Re: [PR] [CALCITE-5093] Quantified comparison operators (e.g. ANY) should support ARRAY arguments [calcite] via GitHub
  • Re: [PR] [CALCITE-5093] Quantified comparison operators (e.g. ANY) should support ARRAY arguments [calcite] via GitHub
  • Re: [PR] [CALCITE-5093] Quantified comparison operators (e.g. ANY) should support ARRAY arguments [calcite] via GitHub
  • Re: [PR] [CALCITE-5093] Quantified comparison operators (e.g. ANY) should support ARRAY arguments [calcite] via GitHub
• [PR] [CALCITE-5597] SELECT DISTINCT query with ORDER BY column will get error result error result [calcite] via GitHub
  • Re: [PR] [CALCITE-5597] SELECT DISTINCT query with ORDER BY column will get error result error result [calcite] via GitHub
  • Re: [PR] [CALCITE-5597] SELECT DISTINCT query with ORDER BY column will get error result error result [calcite] via GitHub
  • Re: [PR] [CALCITE-5597] SELECT DISTINCT query with ORDER BY column will get error result error result [calcite] via GitHub
  • Re: [PR] [CALCITE-5597] SELECT DISTINCT query with ORDER BY column will get error result error result [calcite] via GitHub
  • Re: [PR] [CALCITE-5597] SELECT DISTINCT query with ORDER BY column will get error result error result [calcite] via GitHub
  • Re: [PR] [CALCITE-5597] SELECT DISTINCT query with ORDER BY column will get error result error result [calcite] via GitHub
  • Re: [PR] [CALCITE-5597] SELECT DISTINCT query with ORDER BY column will get error result error result [calcite] via GitHub
  • Re: [PR] [CALCITE-5597] SELECT DISTINCT query with ORDER BY column will get error result error result [calcite] via GitHub
• (calcite) branch main updated: [CALCITE-7351] Make getMaxNumericScale() and getMaxNumericPrecision() final asolimando
• (calcite) branch main updated: [CALCITE-7337] Add age function (enabled in PostgreSQL library) zhenchen
• (calcite) branch main updated: [CALCITE-7348] Remove redundant extraction correlation variables when Trim Project Fields xiong
• (calcite) branch main updated: [CALCITE-6066] Add HYPOT function (enabled in Spark library) xuzifu666
• (calcite-site) branch main updated: Website deployed from calcite@533a61520bbb77cab331ce931da8ee921891f144 asf-ci-deploy
• (calcite) branch site updated: Site: Add Thomas Rebele as committer github-bot
• (calcite) branch main updated: Site: Add Thomas Rebele as committer thomasrebele
• (calcite) branch main updated: [CALCITE-7352] Incorrect SqlLibrary enum value used in ClickHouse SQL test xuzifu666
• [PR] [CALCITE-7352] Incorrect SqlLibrary enum value used in ClickHouse SQL test [calcite] via GitHub
  • Re: [PR] [CALCITE-7352] Incorrect SqlLibrary enum value used in ClickHouse SQL test [calcite] via GitHub
  • Re: [PR] [CALCITE-7352] Incorrect SqlLibrary enum value used in ClickHouse SQL test [calcite] via GitHub
  • Re: [PR] [CALCITE-7352] Incorrect SqlLibrary enum value used in ClickHouse SQL test [calcite] via GitHub
• (calcite) branch main updated: [CALCITE-7350] Missing allowEmptyOutputFromRewrite parameter in TopDownGeneralDecorrelator.unnestInternal silun
• [PR] [CALCITE-6066] Add HYPOT function (enabled in Spark library) [calcite] via GitHub
  • Re: [PR] [CALCITE-6066] Add HYPOT function (enabled in Spark library) [calcite] via GitHub
  • Re: [PR] [CALCITE-6066] Add HYPOT function (enabled in Spark library) [calcite] via GitHub
  • Re: [PR] [CALCITE-6066] Add HYPOT function (enabled in Spark library) [calcite] via GitHub
  • Re: [PR] [CALCITE-6066] Add HYPOT function (enabled in Spark library) [calcite] via GitHub
  • Re: [PR] [CALCITE-6066] Add HYPOT function (enabled in Spark library) [calcite] via GitHub
  • Re: [PR] [CALCITE-6066] Add HYPOT function (enabled in Spark library) [calcite] via GitHub
  • Re: [PR] [CALCITE-6066] Add HYPOT function (enabled in Spark library) [calcite] via GitHub
  • Re: [PR] [CALCITE-6066] Add HYPOT function (enabled in Spark library) [calcite] via GitHub
  • Re: [PR] [CALCITE-6066] Add HYPOT function (enabled in Spark library) [calcite] via GitHub
  • Re: [PR] [CALCITE-6066] Add HYPOT function (enabled in Spark library) [calcite] via GitHub
• [PR] [CALCITE-6829] MSSQL dialect incorrectly translates of SELECT TRUE [calcite] via GitHub
  • Re: [PR] [CALCITE-6829] MSSQL dialect incorrectly translates of SELECT TRUE [calcite] via GitHub
  • Re: [PR] [CALCITE-6829] MSSQL dialect incorrectly translates of SELECT TRUE [calcite] via GitHub
  • Re: [PR] [CALCITE-6829] MSSQL dialect incorrectly translates of SELECT TRUE [calcite] via GitHub
  • Re: [PR] [CALCITE-6829] MSSQL dialect incorrectly translates of SELECT TRUE [calcite] via GitHub
  • Re: [PR] [CALCITE-6829] MSSQL dialect incorrectly translates of SELECT TRUE [calcite] via GitHub
  • Re: [PR] [CALCITE-6829] MSSQL dialect incorrectly translates of SELECT TRUE [calcite] via GitHub
  • Re: [PR] [CALCITE-6829] MSSQL dialect incorrectly translates of SELECT TRUE [calcite] via GitHub
  • Re: [PR] [CALCITE-6829] MSSQL dialect incorrectly translates of SELECT TRUE [calcite] via GitHub
  • Re: [PR] [CALCITE-6829] MSSQL dialect incorrectly translates of SELECT TRUE [calcite] via GitHub
  • Re: [PR] [CALCITE-6829] MSSQL dialect incorrectly translates of SELECT TRUE [calcite] via GitHub
  • Re: [PR] [CALCITE-6829] MSSQL dialect incorrectly translates of SELECT TRUE [calcite] via GitHub
  • Re: [PR] [CALCITE-6829] MSSQL dialect incorrectly translates of SELECT TRUE [calcite] via GitHub
  • Re: [PR] [CALCITE-6829] MSSQL dialect incorrectly translates of SELECT TRUE [calcite] via GitHub

• Earlier messages
• Later messages