Adjust binging security test to server behavioral change (#2588)

Author: sfc-gh-pczajka

test/integ/test_cursor_binding.py

@@ -42,21 +42,38 @@ def test_binding_security(conn_cnx, db_parameters):
 
             # SQL injection safe test
             # Good Example
-            with pytest.raises(ProgrammingError):
-                cnx.cursor().execute(
-                    "SELECT * FROM {name} WHERE aa=%s".format(
-                        name=db_parameters["name"]
-                    ),
-                    ("1 or aa>0",),
+            # server behavior change: this no longer raises an error, but returns an empty result set
+            try:
+                res = (
+                    cnx.cursor()
+                    .execute(
+                        "SELECT * FROM {name} WHERE aa=%s".format(
+                            name=db_parameters["name"]
+                        ),
+                        ("1 or aa>0",),
+                    )
+                    .fetchall()
                 )
-
-            with pytest.raises(ProgrammingError):
-                cnx.cursor().execute(
-                    "SELECT * FROM {name} WHERE aa=%(aa)s".format(
-                        name=db_parameters["name"]
-                    ),
-                    {"aa": "1 or aa>0"},
+                assert res == []
+            except ProgrammingError:
+                # old server behavior: OK
+                pass
+
+            try:
+                res = (
+                    cnx.cursor()
+                    .execute(
+                        "SELECT * FROM {name} WHERE aa=%(aa)s".format(
+                            name=db_parameters["name"]
+                        ),
+                        {"aa": "1 or aa>0"},
+                    )
+                    .fetchall()
                 )
+                assert res == []
+            except ProgrammingError:
+                # old server behavior: OK
+                pass
 
             # Bad Example in application. DON'T DO THIS
             c = cnx.cursor()