From 2ff57fe69a1a4149710cdb2635a74c543b1d69d2 Mon Sep 17 00:00:00 2001 From: Miguel Fernandez Date: Mon, 13 Nov 2023 11:18:29 +0100 Subject: [PATCH] test(qe): exclude json nested shorthand in MySQL 5.6 --- .../query-engine-tests/tests/queries/filters/json.rs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/query-engine/connector-test-kit-rs/query-engine-tests/tests/queries/filters/json.rs b/query-engine/connector-test-kit-rs/query-engine-tests/tests/queries/filters/json.rs index 5440ff8218f8..2b4b880b4975 100644 --- a/query-engine/connector-test-kit-rs/query-engine-tests/tests/queries/filters/json.rs +++ b/query-engine/connector-test-kit-rs/query-engine-tests/tests/queries/filters/json.rs @@ -209,7 +209,7 @@ mod json { // The external runner for driver adapters, in spite of the protocol being used in the test matrix // uses the JSON representation of queries, so this test should not apply to driver adapters (exclude(JS)) - #[connector_test(schema(json_opt), exclude(JS))] + #[connector_test(schema(json_opt), exclude(JS, MySQL(5.6)))] async fn nested_not_shorthand(runner: Runner) -> TestResult<()> { // Those tests pass with the JSON protocol because the entire object is parsed as JSON. // They remain useful to ensure we don't ever allow a full JSON filter input object type at the schema level.