Fix of the memory leak. It could occur if prepare, or direct executio…

…n in case of 10.2, failed, and Stmt handler reused.

Alse removed unused field from Stmt struct and its references(was only
freed in few places).

ma_odbc.h

@@ -311,7 +311,6 @@ struct st_ma_odbc_stmt
   MADB_DescRecord           *PutDataRec;
   MADB_Stmt                 *DaeStmt;
   char                      *StmtString;
-  char                      *NativeSql;
   MADB_Stmt                 *PositionedCursor;
   my_bool                   PositionedCommand;
   enum MADB_StmtState       State;

ma_statement.c

@@ -221,7 +221,6 @@ SQLRETURN MADB_StmtFree(MADB_Stmt *Stmt, SQLUSMALLINT Option)
     MADB_FREE(Stmt->result);
     MADB_FREE(Stmt->Cursor.Name);
     MADB_FREE(Stmt->StmtString);
-    MADB_FREE(Stmt->NativeSql);
     MADB_FREE(Stmt->CatalogName);
     MADB_FREE(Stmt->TableName);
     ResetMetadata(&Stmt->metadata, NULL);
@@ -334,7 +333,6 @@ SQLRETURN MADB_StmtExecDirect(MADB_Stmt *Stmt, char *StatementText, SQLINTEGER T
     else
     {
       MADB_FREE(Stmt->StmtString);
-      MADB_FREE(Stmt->NativeSql);
       return ret;
     }
   }
@@ -426,9 +424,12 @@ void MADB_StmtReset(MADB_Stmt *Stmt)
     Stmt->Ird->Header.Count= 0;
 
   case MADB_SS_EMULATED:
+  /* We can have the case, then query did not succeed, and in case of direct execution we wouldn't
+     have ane state set, but some of stuff still needs to be cleaned. Perhaps we could introduce a state
+     for such case, smth like DIREXEC_PREPARED. Would be more proper, but yet overkill */
+  default:
     Stmt->PositionedCommand= 0;
     Stmt->QueryType= MADB_QUERY_NO_RESULT;
-    MADB_FREE(Stmt->NativeSql);
     MADB_FREE(Stmt->StmtString);
     Stmt->State= MADB_SS_INITED;
     MADB_CLEAR_ERROR(&Stmt->Error);