feat(snowflake)!: support transpilation of BOOLAND from snowflake to duckdb

[fivetran-felixhuang]

https://docs.snowflake.com/en/sql-reference/functions/booland

https://duckdb.org/docs/stable/sql/expressions/logical_operators

Snowflake's BOOLAND operates on numeric types and NULL, while DuckDB's AND operates on boolean values and NULL.

If we transform each argument expr for the Snowflake BOOLAND to expr == NULL ? NULL : expr != 0, we can use DuckDB's built in AND operator to do the rest

[VaggelisD]

while DuckDB's AND operates on boolean values and NULL

Why is that the case? The previous transpilation looks fine:

snowflake> SELECT BOOLAND(1, -2), BOOLAND(12, 0), BOOLAND(4, NULL);
TRUE | FALSE | NULL



D SELECT ((1) AND (-2)), (12 AND 0), (4 AND NULL);
┌────────────┬────────────┬──────────────┐
│ (1 AND -2) │ (12 AND 0) │ (4 AND NULL) │
│  boolean   │  boolean   │   boolean    │
├────────────┼────────────┼──────────────┤
│ true       │ false      │ NULL         │
└────────────┴────────────┴──────────────┘

[fivetran-felixhuang]

while DuckDB's AND operates on boolean values and NULL

Why is that the case? The previous transpilation looks fine:

snowflake> SELECT BOOLAND(1, -2), BOOLAND(12, 0), BOOLAND(4, NULL);
TRUE | FALSE | NULL



D SELECT ((1) AND (-2)), (12 AND 0), (4 AND NULL);
┌────────────┬────────────┬──────────────┐
│ (1 AND -2) │ (12 AND 0) │ (4 AND NULL) │
│  boolean   │  boolean   │   boolean    │
├────────────┼────────────┼──────────────┤
│ true       │ false      │ NULL         │
└────────────┴────────────┴──────────────┘

You are right, the transpilation works already. I assumed that DuckDB's AND operator only works on boolean values