• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

ColdFusion 2016 and Stored Procedure -dbvarname

Participant ,
Nov 26, 2016 Nov 26, 2016

Copy link to clipboard

Copied

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>

Views

1.2K

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Community Expert , Dec 26, 2016 Dec 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

...

Votes

Translate

Translate
Adobe Employee ,
Dec 23, 2016 Dec 23, 2016

Copy link to clipboard

Copied

Hi Weezerboy,

Could you please tell me the update level of ColdFusion.

Thank You,

Abhishek

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Participant ,
Dec 23, 2016 Dec 23, 2016

Copy link to clipboard

Copied

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

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Dec 26, 2016 Dec 26, 2016

Copy link to clipboard

Copied

LATEST

@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>

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Resources
Documentation