Re: Calling ExecuteSQL from c++ hangs

From: Mike Krolewski <mkrolewski_at_rosetta.org>
Date: Tue, 12 Dec 2000 17:48:21 GMT
Message-ID: <915od1$odi$1_at_nnrp1.deja.com>


In article <915jch$jh6$1_at_nnrp1.deja.com>,   fuckingstupid_at_my-deja.com wrote:
> Using Oracle's ODatabase classes , I'm doing this
>
> ODatabase ODb;
> oresult or = ODb.Open
> ("mydatabase", "myid", "mypassword");
>
> ODb.GetParameters().Add("Name", "Moto",
> OPARAMETER_INVAR, OTYPE_VARCHAR2);
>
> ODb.GetParameters().Add("id", 101,
> PARAMETER_INVAR, OTYPE_NUMBER);
>
> ODb.GetParameters().Add("Action", 55,
> OPARAMETER_INVAR, OTYPE_NUMBER);
>
> ODb.GetParameters().Add("Status", 55,
> OPARAMETER_INVAR, OTYPE_NUMBER);
>
> ODb.GetParameters().Add("ReturnCode", 0,
> OPARAMETER_OUTVAR, OTYPE_NUMBER);
>
> or = ODb.ExecuteSQL("Begin myproc.Update_Status
> (:Name, :id, :Action, :Status, :ReturnCode);
> end;");
>
> ODb.Close();
> OShutdown();
> }
>
> and it makes the execute call and never comes
> home, ever. Not sure what to do now
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
>

The obvious question is what does the 'update_status' procedure look like?

--
Michael Krolewski
Rosetta Inpharmatics
mkrolewski_at_rosetta.org
              Ususual disclaimers


Sent via Deja.com
http://www.deja.com/
Received on Tue Dec 12 2000 - 18:48:21 CET

Original text of this message