Skip to main content
W
weezerboy
Inspiring
November 26, 2016
Answered

ColdFusion 2016 and Stored Procedure -dbvarname

  • November 26, 2016
  • 1 reply
  • 1407 views

There was discussion that ColdFusion was going to deprecate dbvarname with cf2016

I have code like this that works in CF2005 but I am migrating to CF2016 and am having issues with the Stored Procedure -dbvarname

This no longer works

<cfstoredproc datasource="#live#" procedure="ABX1265">

    <cfprocresult name = "resultXML" resultset = "1" >

    <cfprocparam cfsqltype="cf_sql_char" dbvarname="@COMPANY"   type="in" value="#companyCode#" >

    <cfprocparam cfsqltype="cf_sql_char" dbvarname="@ENVIRONMENT" type="in" value="#arguments.environment#">

</cfstoredproc>

  <cfquery name="out2" datasource="LIVE#companyCode#" >

#resultXML#

</cfquery>

This topic has been closed for replies.
Correct answer BKBK

@Weezerboy, I have to assume that, by CF2005 and ColdFusion Enterprise 12.0, you mean Coldfusion 5 and ColdFusion 2016 Enterprise. Yes, dbVarname was deprecated after Coldfusion 5. But it was apparently brought back to life in ColdFusion 11, amid some confusion.

See for example ColdFusion 11 and dbvarname attribute

In any case, what do your log files say? Do you get any error messages? What brand of database management do you use?

Have you tested whether the values of resultXML and LIVE#companyCode# are what you expect? You could debug your code as follows:

<cfstoredproc datasource="#live#" procedure="ABX1265">

    <cfprocresult name = "resultXML" resultset = "1" >

    <cfprocparam cfsqltype="cf_sql_char" dbvarname="@COMPANY"   type="in" value="#companyCode#" >

    <cfprocparam cfsqltype="cf_sql_char" dbvarname="@ENVIRONMENT" type="in" value="#arguments.environment#">

</cfstoredproc>

  <cfoutput>

datasource: LIVE#companyCode#<br>

resultXML: #resultXML#

</cfoutput>

1 reply

A
Community Manager
AbhishekJhaCommunity Manager
Community Manager
December 23, 2016

Hi Weezerboy,

Could you please tell me the update level of ColdFusion.

Thank You,

Abhishek

W
weezerboyAuthor
Inspiring
December 23, 2016

ColdFusion Enterprise 12.0

Patrick Hutchinson | Office: 804-370-6873

<mailto:patrick.hutchinson2@gmail.com> patrick.hutchinson2@gmail.com | <https://www.linkedin.com/profile/preview?locale=en_US&trk=prof-0-sb-preview-primary-button> LinkedIn

BKBK
Community Expert
BKBKCommunity ExpertCorrect answer
Community Expert
December 26, 2016

@Weezerboy, I have to assume that, by CF2005 and ColdFusion Enterprise 12.0, you mean Coldfusion 5 and ColdFusion 2016 Enterprise. Yes, dbVarname was deprecated after Coldfusion 5. But it was apparently brought back to life in ColdFusion 11, amid some confusion.

See for example ColdFusion 11 and dbvarname attribute

In any case, what do your log files say? Do you get any error messages? What brand of database management do you use?

Have you tested whether the values of resultXML and LIVE#companyCode# are what you expect? You could debug your code as follows:

<cfstoredproc datasource="#live#" procedure="ABX1265">

    <cfprocresult name = "resultXML" resultset = "1" >

    <cfprocparam cfsqltype="cf_sql_char" dbvarname="@COMPANY"   type="in" value="#companyCode#" >

    <cfprocparam cfsqltype="cf_sql_char" dbvarname="@ENVIRONMENT" type="in" value="#arguments.environment#">

</cfstoredproc>

  <cfoutput>

datasource: LIVE#companyCode#<br>

resultXML: #resultXML#

</cfoutput>

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices