|
Hi all,
How to use callable statements for JDBC request? Please help me; I want to use the same for sending parameters at run time if possible From Gopal "Legal Disclaimer: This electronic message and all contents contain information from Cybage Software Private Limited which may be privileged, confidential, or otherwise protected from disclosure. The information is intended to be for the addressee(s) only. If you are not an addressee, any disclosure, copy, distribution, or use of the contents of this message is strictly prohibited. If you have received this electronic message in error please notify the sender by reply e-mail to and destroy the original message and all copies. Cybage has taken every reasonable precaution to minimize the risk of malicious content in the mail, but is not liable for any damage you may sustain as a result of any malicious content in this e-mail. You should carry out your own malicious content checks before opening the e-mail or attachment." www.cybage.com |
|
Googling suggests that the format is
{call procedurename(param1,...)} Try this with fixed parameter values first. Or ideally with a procedure that does not need parameters, then try with one that needs parameters. You can then try replacing some parameters with JMeter variable references, for example: {call procedurename('${TEXT}',...)} where TEXT is a JMeter variable containing some text to be sent to the procedure. Note that the variable reference needs to be enclosed in quotes so that it is passed as a string to the stored procedure. I don't know Oracle, so I may have got the quote character wrong - perhaps it should be " rather than '. On 08/12/06, Labudu Gopanna <[hidden email]> wrote: > Hi all, > > How to use callable statements for JDBC request? > > Please help me; I want to use the same for sending parameters at run > time if possible > > > > From > > Gopal > > > "Legal Disclaimer: This electronic message and all contents contain information from Cybage Software Private Limited which may be privileged, confidential, or otherwise protected from disclosure. The information is intended to be for the addressee(s) only. If you are not an addressee, any disclosure, copy, distribution, or use of the contents of this message is strictly prohibited. If you have received this electronic message in error please notify the sender by reply e-mail to and destroy the original message and all copies. Cybage has taken every reasonable precaution to minimize the risk of malicious content in the mail, but is not liable for any damage you may sustain as a result of any malicious content in this e-mail. You should carry out your own malicious content checks before opening the e-mail or attachment." > www.cybage.com > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [hidden email] For additional commands, e-mail: [hidden email] |
|
Thanks for reply,
Hi Sebb, Thanks for reply, I have tried with fixed parameter values first. But results are the same. I am using PostgreQSL database it is working fine for select and update statements. -----Original Message----- From: sebb [mailto:[hidden email]] Sent: Friday, December 08, 2006 5:14 PM To: JMeter Users List Subject: Re: How to use callable statements for JDBC request?. Googling suggests that the format is {call procedurename(param1,...)} Try this with fixed parameter values first. Or ideally with a procedure that does not need parameters, then try with one that needs parameters. You can then try replacing some parameters with JMeter variable references, for example: {call procedurename('${TEXT}',...)} where TEXT is a JMeter variable containing some text to be sent to the procedure. Note that the variable reference needs to be enclosed in quotes so that it is passed as a string to the stored procedure. I don't know Oracle, so I may have got the quote character wrong - perhaps it should be " rather than '. On 08/12/06, Labudu Gopanna <[hidden email]> wrote: > Hi all, > > How to use callable statements for JDBC request? > > Please help me; I want to use the same for sending parameters at run > time if possible > > > > From > > Gopal > > > "Legal Disclaimer: This electronic message and all contents contain privileged, confidential, or otherwise protected from disclosure. The information is intended to be for the addressee(s) only. If you are not an addressee, any disclosure, copy, distribution, or use of the contents of this message is strictly prohibited. If you have received this electronic message in error please notify the sender by reply e-mail to and destroy the original message and all copies. Cybage has taken every reasonable precaution to minimize the risk of malicious content in the mail, but is not liable for any damage you may sustain as a result of any malicious content in this e-mail. You should carry out your own malicious content checks before opening the e-mail or attachment." > www.cybage.com > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [hidden email] For additional commands, e-mail: [hidden email] --------------------------------------------------------------------- To unsubscribe, e-mail: [hidden email] For additional commands, e-mail: [hidden email] |
|
What are the results?
Are you sure that the PostgreSQL JDBC driver supports callable statements? On 08/12/06, Labudu Gopanna <[hidden email]> wrote: > Thanks for reply, > Hi Sebb, > Thanks for reply, > I have tried with fixed parameter values first. > But results are the same. I am using PostgreQSL database it is working > fine for select and update statements. > > > > -----Original Message----- > From: sebb [mailto:[hidden email]] > Sent: Friday, December 08, 2006 5:14 PM > To: JMeter Users List > Subject: Re: How to use callable statements for JDBC request?. > > Googling suggests that the format is > > {call procedurename(param1,...)} > > Try this with fixed parameter values first. > Or ideally with a procedure that does not need parameters, then try > with one that needs parameters. > > You can then try replacing some parameters with JMeter variable > references, > for example: > > {call procedurename('${TEXT}',...)} > > where TEXT is a JMeter variable containing some text to be sent to the > procedure. > > Note that the variable reference needs to be enclosed in quotes so > that it is passed as a string to the stored procedure. > > I don't know Oracle, so I may have got the quote character wrong - > perhaps it should be " rather than '. > > > > On 08/12/06, Labudu Gopanna <[hidden email]> wrote: > > Hi all, > > > > How to use callable statements for JDBC request? > > > > Please help me; I want to use the same for sending parameters at run > > time if possible > > > > > > > > From > > > > Gopal > > > > > > "Legal Disclaimer: This electronic message and all contents contain > information from Cybage Software Private Limited which may be > privileged, confidential, or otherwise protected from disclosure. The > information is intended to be for the addressee(s) only. If you are not > an addressee, any disclosure, copy, distribution, or use of the contents > of this message is strictly prohibited. If you have received this > electronic message in error please notify the sender by reply e-mail to > and destroy the original message and all copies. Cybage has taken every > reasonable precaution to minimize the risk of malicious content in the > mail, but is not liable for any damage you may sustain as a result of > any malicious content in this e-mail. You should carry out your own > malicious content checks before opening the e-mail or attachment." > > www.cybage.com > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [hidden email] > For additional commands, e-mail: [hidden email] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [hidden email] > For additional commands, e-mail: [hidden email] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [hidden email] For additional commands, e-mail: [hidden email] |
| Powered by Nabble | Edit this page |
