tracker issue : CF-3916950

select a category, or use search below
(searches all categories and all time range)
Title:

[ANeff] ER for: auto-prepend dbvarname prefix if omitted

| View in Tracker

Status/Resolution/Reason: Needs Review//

Reporter/Name(from Bugbase): Aaron Neff / Aaron Neff (Aaron Neff)

Created: 01/07/2015

Components: Database

Versions: 11.0

Failure Type: Enhancement Request

Found In Build/Fixed In Build: CF11_Final /

Priority/Frequency: Trivial / Unknown

Locale/System: English / Win All

Vote Count: 10

CF11 Update 3 restored cfprocparam's deprecated dbvarname functionality. Thanks! It would be further helpful if dbvarname's db-specific prefix was auto-prepended if it was omitted. (credit for this idea goes to Adam Cameron)

Copying my 1:29:15 AM GMT+00:00 Jan 6, 2015 comment from #3865064 to here:
-----------
I do realize Update 3 simply restored the deprecated behavior, but I also would like to echo Adam's statement/question: "why if SQL Server and Oracle NEED special prefixes, and you KNOW this, why the CF code doesn't prepend them".

This reminds me of when cfquery, for INSERT queries, returned a db-specific variable name containing the automatically-generated ID. Later, CF simplified this and supported all databases w/ a "result_name.GENERATEDKEY" variable. Can't CF offer the same simplicity for these parameter prefixes (i.e. simply auto-prepend the db-specific prefix if it was omitted)?
-----------

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3916950

External Customer Info:
External Company:  
External Customer Name: itisdesign
External Customer Email:

Attachments:

Comments:

Very much required :) This should help everyone...Including new developments also.
Comment by External U.
9078 | January 07, 2015 12:53:21 AM GMT
Very much necessary. When can this be released? :)
Vote by External U.
9079 | January 07, 2015 12:53:44 AM GMT
+1 I agree with this. Auto prepend of db specific characters in dbvaraname will help a lot
Vote by External U.
9080 | January 07, 2015 12:55:13 AM GMT
+1. Can't see any backwards compat issues with this? Just need to check if the usage already has the prefix for the given DB platform, and if not: append it.
Vote by External U.
9081 | January 07, 2015 01:29:33 AM GMT
+1. And for those already prepending the character, it should see this and not prepend it again.
Vote by External U.
9082 | January 07, 2015 10:53:18 AM GMT
Do this. I shouldn't have to care about these sorts of DB specifics.
Vote by External U.
9083 | January 07, 2015 01:10:02 PM GMT
This would certainly help me having to make a multitude of changes to my code since updating CF to version 11
Vote by External U.
9084 | January 22, 2015 03:04:49 PM GMT
This is a must, a lot of code will not work without this fix.
Vote by External U.
9085 | January 27, 2015 10:31:38 AM GMT
This will make our migration to CF 11 possible.
Vote by External U.
9086 | February 13, 2015 10:08:59 AM GMT
I completely agree. Perhaps you could provide an accompanying setting to enable/disable this functionality. If you didn't want to do it automagically, perhaps you could add another DSN setting, something like "Store Procedure dbVarName prefix"
Vote by External U.
9087 | June 05, 2015 11:54:13 AM GMT
This was working fine untill cf10, when we moved this to CF11 it was too bad that we had to change all the procs with this settings. Better we have the old functionality
Vote by External U.
9088 | July 21, 2015 07:32:11 AM GMT