This is a discussion on Java calling a stored procedure... within the Informix forums, part of the Database Server Software category; --> Ok... for those java jdbc gurus out there... In Java, you open a connection, then create a statement object. ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Ok... for those java jdbc gurus out there... In Java, you open a connection, then create a statement object. >From this statement object, you executeUpdate(<string>) where <string> is your SQL statement. When executing a stored procedure that doesn't return anything, Java is recommending that you surround the stored procedure call with {}. The question is why? Why are calling stored procedures different from executing any other SQL statement? TIA! -G __________________________________________________ _______________ Mortgage rates as low as 4.625% - Refinance $150,000 loan for $579 a month. Intro*Terms http://www.NexTag.com |
| ||||
| Ian, A statement string such as "{call procedure-name(parameters)}" is converted to the database-specific syntax, making your Java application more portable between database products. -- Regards, Doug Lawry www.douglawry.webhop.org "Ian Michael Gumby" <im_gumby@hotmail.com> wrote in message news:mailman.227.1171914232.10648.informix-list@iiug.org... > > Ok... for those java jdbc gurus out there... > > In Java, you open a connection, then create a statement object. > >>From this statement object, you executeUpdate(<string>) where <string> is > your SQL statement. > > > When executing a stored procedure that doesn't return anything, Java is > recommending that you surround the stored procedure call with {}. > > The question is why? > > Why are calling stored procedures different from executing any other SQL > statement? > > TIA! > > -G |