tracker issue : CF-3489160

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

Bring the dbvarname attribute back for cfprocparam

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

Reporter/Name(from Bugbase): Adam Cameron / Adam Cameron (Adam Cameron)

Created: 01/24/2013

Components: Database

Versions: 10.0

Failure Type: Enhancement Request

Found In Build/Fixed In Build: Final / CF10_Update14

Priority/Frequency: Major / Unknown

Locale/System: English / Platforms All

Vote Count: 8

Extract from my blog post (http://adamcameroncoldfusion.blogspot.co.uk/2013/01/bring-back-named-params-for.html):

From the docs: "Changed the dbvarname attribute behavior: it is now ignored for all drivers. ColdFusion uses JDBC 2.2 and does not support named parameters. This is deprecated."

[...]
Now, whilst JDBC 2.2 indeed didn't support named params, JDBC 3.0 did support them, and JDBC 3.0 was released a year before CFMX was. [...]  We're up to JDBC 4.1.

[...]

There are a number of tickets in the bugbase with people asking for this functionality. Here's a couple: 3114260, 3035825; the latter marked as a duplicate of 3035675, which doesn't exist. Oh, they're both closed. What pisses me off is that in the old system there's a ticket 72534 which covers the same ground and is still open, but this seemingly never migrated to the new system.

Cheers.

-- 
Adam

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

Watson Bug ID:	3489160

Deployment Phase:	Release Candidate

External Customer Info:
External Company:  
External Customer Name: Adam Cameron.
External Customer Email:  
External Test Config: My Hardware and Environment details:

Attachments:

Comments:

This is supported in current JDBC drivers for the most common databases. Since it was only removed due to lack of support in JDBC 2.2 (which was many, many years ago), it's long overdue for being reintroduced!
Vote by External U.
16517 | January 24, 2013 04:00:02 PM GMT
This should be re-instated.
Vote by External U.
16518 | January 25, 2013 03:09:59 AM GMT
This would be really useful, and save much time coding whenever input params are reorganised in a stored proc.
Vote by External U.
16519 | January 25, 2013 03:33:22 AM GMT
I'm waiting this back last 8 years... I'm not sure how many errors occurred just because CF supports only positions for params and somebody changed SP.
Vote by External U.
16520 | January 27, 2013 07:27:34 AM GMT
Every other language we work with supports named parameters. Our SQL Server stored procedures occasionally get new defaulted parameter values and it would be nice to be able to order them logically instead of always needing to put them at the end in case it would break ColdFusion. Also sometimes earlier parameter values would be best left with their default values and the application layer doesn't need to know what those are; especially in cases where magic numbers are used.
Vote by External U.
16521 | March 28, 2013 07:27:45 AM GMT
This would make changes in stored procedures much easier to manage, especially when most of the parameters are left to default values.
Vote by External U.
16522 | March 28, 2013 07:31:51 AM GMT
This ticket seems to have been logged four months ago and it's still "Unverified". It really is not helpful to not be able to specify named arguments so can you please treat this issue a bit more seriously?
Vote by External U.
16523 | May 17, 2013 05:25:02 AM GMT
When we upgraded to JDBC 3.0, not all the drivers were implementing it correctly and in fact some of them were violating the contract where they would say that they support it but it did not actually work. Hopefully, by now all the drivers would be supporting it. Lets take it up. Even if some drivers give a wrong information, we can let it throw error. The application will anyway know during its testing that named parameters are not working for a particular DB/driver and they can either change the driver or change it to positional params.
Comment by Rupesh K.
16515 | May 20, 2013 11:03:26 PM GMT
It is incredibly frustrating to not have named parameters in ColdFusion. How exactly is one supposed to make "enterprise" applications by having to pass in null values for hundreds of optional parameters per stored procedure? This is outrageous to say the least.
Comment by External U.
16516 | October 18, 2013 10:17:30 AM GMT
This features is CRITICAL. It should be dealt with of HIGH IMPORTANCE!!
Vote by External U.
16524 | October 18, 2013 10:17:56 AM GMT