tracker issue : CF-4198196

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

Remove Query.cfc functions as it's broken and won't be fixed

| View in Tracker

Status/Resolution/Reason: To Test//TooManySideEffects

Reporter/Name(from Bugbase): John Whish / John Whish ()

Created: 12/15/2016

Components: Database, CFQuery

Versions: 2016

Failure Type: Data Corruption

Found In Build/Fixed In Build: All 2016 builds /

Priority/Frequency: Normal /

Locale/System: / Platforms All

Vote Count: 5

Problem Description:

As raised in this ticket :

Response was :

Its a valid bug but there is no active development on these CFCs and we recommend to use QueryExecute function. So closing this issue.
Please let us know if you face any issue related to QueryExecute.

Comment by Nimit Sharma

So, as QueryExecute will not be fixed, then you should deprecate and remove `QueryExecute` - if it is not safe to use then people should not be using it. Simply doing nothing is not a great approach. Either fix it if you leave the method in or remove it. Do not include broken functionality.



Title should be: **Remove Query.cfc functions as it's broken and won't be fixed** If someone has edit rights please update the title. Thanks! QueryExecute is the correct approach.
Comment by John W.
1407 | December 15, 2016 10:36:48 AM GMT
The title is the exact wrong recommendation. QueryExecute is what should be used.
Comment by James M.
1408 | January 08, 2017 05:12:01 PM GMT
There needs to be a way to warn users on calling a deprecated function
Vote by James M.
1409 | January 08, 2017 05:12:42 PM GMT
+1 ...........
Vote by Aaron N.
27724 | May 09, 2018 01:24:50 AM GMT