It's admittedly very good (if not best) practice. Sounds like you're doing the same sort of thing with your CFC methods that I used to do with custom-tags. Convenient to be able to call them using a structure -- the form scope for instance -- so if you just set all your form fields to match the parameter names then you can <cfinvoke argumentcollection="#form#"> (I was of course using <cfmodule attributecollection="#form#">) -- helps to loosen the coupling, so if your parameters change you've got fewer places they need to be updated. Then I discovered what I did about JDBC and automated the sp-call, so now I'm down from 3 to 2 to just 1 place where the parameters are specified (outside the db) and that's the form fields. Though I haven't used any sp's recently.
> Yes - I found that by ordering them correctly - AND > specifying the dbvarname > - it actually worked as a code commenter more than > anything for me - as I > knew w/o having to strain through the code which value was > being specified > for what param - > The @var stood out more than all the #var#'s that are in > the code - > That was my practice anyway - > Kevin Penny > www.hotgigs.com > -----Original Message----- > From: S. Isaac Dealey [mailto:[EMAIL PROTECTED] > Sent: Friday, May 20, 2005 10:56 AM > To: CF-Talk > Subject: RE: CFPROCPARAM Help Needed > That depends entirely on how much you actually relied on > the dbvarname > attribute. If most of your procedures have only one > argument or you > nearly always provide your cfprocparam arguments in the > same order > they're declared in the procedure script, you're right. On > the other > hand if you have a lot of cfstoredproc tags where the > cfprocparam tags > are randomly or semi-randomly ordered but used the > dbvarname attribute > to associate them then you'll get errors more often than > not. >> Good point - eventually you may look at this - but I'm >> using cf6 and cf7 >> with no issues on this - it will be 'ignored' more than >> it >> would be errand. >> Kevin >> -----Original Message----- >> From: S. Isaac Dealey [mailto:[EMAIL PROTECTED] >> Sent: Friday, May 20, 2005 10:21 AM >> To: CF-Talk >> Subject: RE: CFPROCPARAM Help Needed >>> As it is cf5 - you can ignore the depreciation comments >>> - >> Except that if they plan to upgrade ever, it will be >> easier if they >> don't rely on dbvarname sooner than later... In this case >> it won't >> matter because the sp only has one parameter, just >> saying. >> :) s. isaac dealey 954.522.6080 new epoch : isn't it time for a change? add features without fixtures with the onTap open source framework http://www.fusiontap.com http://coldfusion.sys-con.com/author/4806Dealey.htm ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application http://www.houseoffusion.com/banners/view.cfm?bannerid=48 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:207286 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
