Thanx for cross-referencing that. So it sounds like a doc bug in that it is not clearly documented in CFMX that dbvarname is ignored (the docs seem to indicate named value pairs still work).
On Tuesday, Oct 22, 2002, at 00:41 US/Pacific, Ken Wilson wrote: > FWIW, whoever wrote the Code Analyzer for CFMX knows it. Here's the > text of > what it tells you when it encounters dbvarname: > > ### > > Dbvarname Info > The DBVARNAME attribute for CFPROCPARAM is ignored in ColdFusion MX. > > How to Fix > If your application is dependent on name/value CFPROCPARAM entries, > you must > change them so the parameters are specified positionally. > > ### > > And here's some of what the docs say: > > dbVarName > Required for named notation > Parameter name that corresponds to the name of the parameter in the > stored > procedure. > > CFPROCPARAM in the CFML Reference > Usage > Use this tag to identify stored procedure parameters and their data > types. > Code one cfprocparam tag for each parameter. The parameters that you > code > vary based on parameter type and DBMS. The order in which you code > cfprocparam tags depends on whether the stored procedure uses > positional or > named notation: > > Positional notation: ColdFusion passes parameters to the stored > procedure in > the order in which they are defined > Named notation: The dbVarName for the parameter must correspond to the > variable name in the stored procedure on the server. > > > > > > -----Original Message----- > From: Sean A Corfield [mailto:sean@;corfield.org] > Sent: Monday, October 21, 2002 11:17 PM > To: CF-Talk > Subject: cfprocparam / dbvarname issue? > > >> This topic is very off topic for CF-Talk. If this is a technical >> question, please repost under a different subject. > > Nice to see the thread-shifter works :) > > On Sunday, Oct 20, 2002, at 10:50 US/Pacific, S. Isaac Dealey wrote: >> My only specific issue at the moment is to either have the dbvarname >> attribute for <cfprocparam> pass the parameter to the stored procedure >> call >> by name, or properly document the fact that dbvarname currently seems >> to be >> solely for the benefit of the developer reading the code as it doesn't >> affect the stored procedure call. Beyond that I'm pretty happy. :) > > I spoke to a couple of folks on the product team and they didn't seem > to be aware of this as an issue. Could you create a simple, > self-contained test case that shows exactly what the problem is and > then submit it as a bug (either as a code bug or a doc bug) via the > standard wishlist form? > > Of course, if you've *already* submitted that, Vern or I can follow-up > to see what happened to the issue internally... > > Sean A Corfield -- http://www.corfield.org/blog/ > Sean A Corfield -- http://www.corfield.org/blog/ "If you're not annoying somebody, you're not really alive." -- Margaret Atwood ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm
