Correct determination of the names of the bind variables in prepared SQL

tatements (which behaves a little differently from PL/SQL statements).

Author: anthony-tuininga

odpi

@@ -1982,7 +1982,8 @@ static PyObject *Cursor_BindNames(udt_Cursor *self, PyObject *args)
     }
 
     // get the bind names
-    if (dpiStmt_getBindNames(self->handle, numBinds, names, nameLengths) < 0) {
+    if (dpiStmt_getBindNames(self->handle, &numBinds, names,
+            nameLengths) < 0) {
         PyMem_Free((void*) names);
         PyMem_Free(nameLengths);
         return Error_RaiseAndReturnNull();

src/Cursor.c

@@ -238,6 +238,8 @@ def testBindNames(self):
                 ":h + :i + :j + :k + :l; end;")
         self.assertEqual(self.cursor.bindnames(),
                 ["A", "B", "C", "D", "E", "F", "G", "H", "I", "J", "K", "L"])
+        self.cursor.prepare("select :a * :a + :b * :b from dual")
+        self.assertEqual(self.cursor.bindnames(), ["A", "B"])
 
     def testBadPrepare(self):
         """test that subsequent executes succeed after bad prepare"""