> S. Isaac Dealey wrote: >> Yea, it turned out to be the cf_sql_date that was causing >> the "wrong number >> of parameters" error message... so changing that to >> cf_sql_timestamp solved >> the problem... Better support for cfstoredproc ( naming >> and better error >> handling in particular. ) would be _great_ to see from >> the folks at MM... >> I'll probably toy with it some once I start working with >> it on MX just to >> see if any improvements came with the new J2EE platform.
> my biggest peve with the cf query/stored proc param > support is that > there is no null="AUTO" option... You mean value="#blah#" and then passing null if there is no variable named #blah#? ... I can't think of any other way CF would know to pass a null... The other thing that really gets me is that with <cfquery> blah blah</cfquery> , no matter how many variables I put in it, as long as I stay away from <cfqueryparam> I get nice clean sql text in the debugging output that I can throw into query analyzer for comparison... If I use cfqueryparam or if I go to a cfstoredproc tag, I get nothing in the debugging output where those are used... Isaac Certified Advanced ColdFusion 5 Developer www.turnkey.to 954-776-0046 ______________________________________________________________________ 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 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
