Comments by Shruti Sagar Mishra

Shruti Sagar Mishra 10-Nov-13 7:58am View

Now this is embarrassing,,
I tried to run the procedure manually it was working fine.
But I came across a new funny situation.
I Changed the
mycommand.parameters.addwithvalue to mycommand.parameters.add
And rest all I put same, and this time worked.
Now the question is infact the .add property is now obsolete , everywhere at mysql references they have mentioned to use addwithValue instead of add, then howcome this is failing.
SO right now I have chnaged the function for parameter.add statement,But I am getting warnings for the same .I can proceed with this but doesnt look neat to me

Shruti Sagar Mishra 9-Nov-13 23:50pm View

I have checked it. But this is the way to declare an output parameter , i/p and o/p parameter declaration is same , apart from the fact that in o/p we need to provide the type of the parameter instead of the actual value as I have given in the code

Shruti Sagar Mishra 9-Nov-13 23:48pm View

I checked it. This is the way we declare the output parameter fr a procedure
parameter is declaration different for input parameter we declare the value of the parameter
for output parameter we provide the type of the parameter instead.

Shruti Sagar Mishra 9-Nov-13 9:50am View

Thanks for the reply ..I agree that the name of the function is wrong I will update this function.
But actually this returning a varchar.So I dont think would be the problem here, apart from the exception the insert query is working perfectly fine in the procedure stated above.

Shruti Sagar Mishra 27-Jun-13 9:17am View

Please clarity your quetion..
Are you trying to implement a Nested dropdown type situation here..

Shruti Sagar Mishra 27-Jun-13 9:09am View

Thanks Pheonyx...
It really helped alot

Comments by Shruti Sagar Mishra (Top 6 by date)