tracker issue : CF-3814079

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

datasource attribute on <cfinsert> should no longer be required

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

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

Created: 08/28/2014

Components: Language

Versions: 11.0

Failure Type:

Found In Build/Fixed In Build: CF11_Final /

Priority/Frequency: Normal / Some users will encounter

Locale/System: English / Platforms All

Vote Count: 2

Listed in the version 2016.0.0.297996 Issues Fixed doc
Verification notes: verified_fixed on August 25, 2019 using build 2016.0.01.298513
It should use the application-wide DSN if it's set.

Same should apply to all DB-using functionality.

This issue probably predates CF11, but that's the version I'm working with.


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

Watson Bug ID:	3814079

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



Fixed Again.
Comment by Nikhil S.
11214 | June 12, 2015 12:51:13 AM GMT
+1 - and it should be optional for <cfupdate> as well
Vote by External U.
11220 | July 22, 2015 01:59:07 PM GMT
So, Nikhil Siddhartha, you had the presence of mind to fix cfinsert because it was right there on the ticket, but it didn't occur to you to also fix cfupdate at the same time? Talk us through the triage process there...?
Comment by Adam C.
11215 | March 21, 2017 08:05:11 AM GMT
*And* you didn't update the docs. That was a pretty half-arsed effort really, wasn't it? dataSource / Required / / Data source; contains table.
Comment by Adam C.
11216 | March 21, 2017 08:07:44 AM GMT
`cfupdate` should like `cfquery` and `cfinsert` and `cfdbinfo` NOT require the datasource attribute - it should be consistent for *all* db tags, so when you updated `cfinsert` then it should have made sense to also check that `cfupdate` didn't also have this issue.
Comment by John W.
11217 | March 21, 2017 09:51:15 AM GMT
To be more clear than I was before, this work is incomplete, so the ticket should not have been closed. cfupdate has not been fixed, and this was part of the original ticket.
Comment by Adam C.
11218 | March 21, 2017 09:51:26 AM GMT
+1 for fixing <cfupdate>
Vote by Carl V.
11221 | March 21, 2017 03:21:48 PM GMT
And my vote comment on 07/22/2015 13:59:07 GMT was ignored.
Comment by Aaron N.
11219 | March 29, 2017 10:16:14 PM GMT
Hi Adobe, I've verified this is fixed in CF2016 Update 1 (build 2016.0.01.298513). Well, specifically cfinsert b/c cfupdate was fixed in a later CF2016 update. Thanks!, -Aaron
Comment by Aaron N.
31197 | August 25, 2019 06:45:43 AM GMT