Re: Stored Procedure: "Danger, Will Robinson!" or not?

Hi Charles, It's a while since I did anything with Stored Procedures, but I seem to remember these warning being produced - I don't think they had any effect, as the procedures worked! I think they are just making sure you know what items you are manipulating!! HTH, Richard. On Tue, 1 Dec 1998, Charles Johnson wrote: > I created and compiled a stored procedure. It compiles and runs without error. > (Appreciably increasing the apparent response time of our Java app.) > > The signature for the procedure is > > create dba procedure get_dheader_note (provid like tr_act_d.prov, > cliid like tr_act_d.cli, > begdate like tr_act_d.session_d, > enddate like tr_act_d.session_d, > begtime like tr_act_d.start_h, > endtime like tr_act_d.start_h) > returning yada...yada...yada...;> > Each of these variables is used in the where clause of a select statement in > the SP. > > I asked that the db-engine send any compile time error messages to a file. > > That file contains the following lines: > > Line 52: identifier(provid) is a variable, not a column > Line 53: identifier(cliid) is a variable, not a column > Line 54: identifier(begdate) is a variable, not a column > Line 54: identifier(enddate) is a variable, not a column > Line 55: identifier(begtime) is a variable, not a column > Line 55: identifier(endtime) is a variable, not a column > > What is Informix trying to tell me? Is it important that I declare these > variables in some way to avoid this mysterious (to me) information? Do I ignore > this information, possibly at my own peril? > > Any insight would be appreciated. > > Cheers-- > Charles