tracker issue : CF-3797144

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

Query of queries strips leading/trailing whitespace

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/Duplicate

Reporter/Name(from Bugbase): Matt Busche / Matt Busche (Matt Busche)

Created: 07/30/2014

Components: Database

Versions: 10.0

Failure Type: Data Corruption

Found In Build/Fixed In Build: Final /

Priority/Frequency: Critical / All users will encounter

Locale/System: English / Linux All

Vote Count: 0

Duplicate ID:	CF-3180467

Problem Description: Running query of queries strips leading/trailing whitespace in the result set

Steps to Reproduce:
<cfset a = queryNew('colwithspaces', 'varchar', [['    ']])>
with spaces - <cfdump var="#len(a.colwithspaces)#"><br>
<cfquery name="b" dbtype="query">
SELECT colwithspaces
after QoQ - <cfdump var="#len(b.colwithspaces)#">

Actual Result: length of column is 0

Expected Result: length of column is 4

Any Workarounds: build the query manually or use Java's removeRows() function to remove rows from the original query.

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

Watson Bug ID:	3797144

External Customer Info:
External Company:  
External Customer Name: Matt Busche
External Customer Email:  
External Test Config: My Hardware and Environment details:

appserver	J2EE

productlevel	Enterprise

productname	ColdFusion Server

productversion	10,0,12,286680

additionalinformation	Linux

arch	x86

encoding	UTF-8

name	UNIX

version	2.6.32-358.23.2.el6.x86_64



Wasn't this bug previously reported in ColdFusion 8 & 9?
Comment by External U.
11489 | July 30, 2014 09:37:59 AM GMT
This was fixed in CF 11.
Comment by Himavanth R.
11490 | July 30, 2014 11:59:41 PM GMT
Himavanth - this is still broken in ColdFusion 10, if we want the fix we have to upgrade? That seems odd, but I guess it doesn't surprise me. There's a reason all of our development is moving to Groovy.
Comment by External U.
11491 | July 31, 2014 06:30:04 AM GMT
Hi Himavanth, Regarding "This was fixed in CF 11.", are you saying customers on the still-supported CF10 have to upgrade to CF11 to get the fix for something that was filed on May 2, 2012 when CF10 didn't even exist? If so, with all respect, that really isn't right - is it? They've been waiting over 2 years. Thanks, -Aaron
Comment by External U.
11492 | November 16, 2014 07:03:56 AM GMT
"when CF10 didn't even exist" should've been "when CF11 didn't even exist"
Comment by External U.
11493 | November 16, 2014 07:04:57 AM GMT