fixed some more test failures

Author: evertlammerts

src/duckdb_py/pyexpression.cpp

@@ -409,6 +409,10 @@ shared_ptr<DuckDBPyExpression> DuckDBPyExpression::LambdaExpression(const py::ob
 		throw py::value_error("Please provide 'lhs' as either a tuple containing strings, or a single string");
 	}
 	auto lambda_expression = make_uniq<duckdb::LambdaExpression>(std::move(lhs), rhs.GetExpression().Copy());
+	// Use the modern `lambda x, y: ...` syntax. The lhs we built (a column ref, or a `row` function for multiple
+	// parameters) is identical to what the named-parameter constructor produces; only the syntax type differs, and
+	// the single-arrow form is now deprecated and errors by default.
+	lambda_expression->GetLambdaSyntaxTypeMutable() = LambdaSyntaxType::LAMBDA_KEYWORD;
 	return make_shared_ptr<DuckDBPyExpression>(std::move(lambda_expression));
 }
 

tests/fast/api/test_duckdb_query.py

@@ -91,9 +91,11 @@ def test_named_param(self):
     def test_named_param_not_dict(self):
         con = duckdb.connect()
 
+        # The missing-parameter names come from an unordered set, so their order is not stable; match all three
+        # regardless of order.
         with pytest.raises(
             duckdb.InvalidInputException,
-            match="Values were not provided for the following prepared statement parameters: name1, name2, name3",
+            match=r"prepared statement parameters: (?=.*\bname1\b)(?=.*\bname2\b)(?=.*\bname3\b)",
         ):
             con.execute("select $name1, $name2, $name3", ["name1", "name2", "name3"])
 
@@ -126,9 +128,10 @@ def test_named_param_excessive(self):
     def test_named_param_not_named(self):
         con = duckdb.connect()
 
+        # Unordered set: match both missing parameters regardless of order.
         with pytest.raises(
             duckdb.InvalidInputException,
-            match="Values were not provided for the following prepared statement parameters: 1, 2",
+            match=r"prepared statement parameters: (?=.*\b1\b)(?=.*\b2\b)",
         ):
             con.execute("select $1, $1, $2", {"name1": 5, "name2": 3})
 

tests/fast/arrow/test_arrow_types.py

@@ -13,11 +13,7 @@ def test_null_type(self, duckdb_cursor):
         arrow_table = pa.Table.from_arrays(inputs, schema=schema)
         duckdb_cursor.register("testarrow", arrow_table)
         rel = duckdb.from_arrow(arrow_table).to_arrow_table()
-        # We turn it to an array of int32 nulls
-        schema = pa.schema([("data", pa.int32())])
-        inputs = [pa.array([None, None, None], type=pa.null())]
-        arrow_table = pa.Table.from_arrays(inputs, schema=schema)
-
+        # NULL type now round-trips faithfully (previously it was coerced to int32)
         assert rel["data"] == arrow_table["data"]
 
     def test_invalid_struct(self, duckdb_cursor):