tracker issue : CF-3217374

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

SQL Server 2008 Geography/geometry/HierarchyID Data Type Error

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

Reporter/Name(from Bugbase): Dave Krause / Dave Krause (Donkey Riptide)

Created: 06/18/2012

Components: Database, JDBC

Versions: 10.0

Failure Type: Non Functioning

Found In Build/Fixed In Build: Final / CF10_Update14

Priority/Frequency: Critical / All users will encounter

Locale/System: English / Win 2008 Server R2 64 bit

Vote Count: 10

Listed in the version Issues Fixed doc
Related Bugs:
CF-3737600 - Similar to

Problem Description: All tables using "geography/geometry/HierarchyID" data type in SQL Server 2008 returning this error: Error Executing Database Query. [Macromedia][SQLServer JDBC Driver]Data type not supported: Unknown: 0xf0 

Steps to Reproduce: Add geography data type to a table, try to run query. Don't even need data in there!

Works fine in CF9 with same datasource settings...

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

Watson Bug ID:	3217374

External Customer Info:
External Company:  
External Customer Name: Donkey Riptide
External Customer Email:  
External Test Config: My Hardware and Environment details: Windows 2008 RD2, SQL Server 2008, IIS 7

Version	 ColdFusion 10,282462

Tomcat Version



Same problem!
Comment by External U.
18976 | June 18, 2012 02:46:24 PM GMT
This affects productivity...because it doesn't work. I have the same problem when querying a table with geographic data.
Vote by External U.
18989 | June 18, 2012 02:46:59 PM GMT
Yes, this is an issue for me too :-)
Vote by External U.
18990 | June 18, 2012 02:54:57 PM GMT
Same problem here too!
Comment by External U.
18977 | June 18, 2012 02:55:26 PM GMT
Running a query with a Geography or Geometry data type (MSSQL) in the "select" portion of the statement, throws an error as error. The data cannot be returned to be used at all unless done in SQL. With more and more needs for spatial data and GIS applications this is a major deal breaker for CF10. I can't be productive if I can't get and use the data...
Vote by External U.
18991 | June 18, 2012 02:57:01 PM GMT
I have this problem for Geography and Geometry data types from MSSQL. There is not elegant fallback but throws an error. CF9 returned this data as a Binary data type.
Comment by External U.
18978 | June 18, 2012 03:03:42 PM GMT
same problem for me, doesn't work, limits productivity just like the guy above said
Vote by External U.
18992 | June 19, 2012 10:25:23 AM GMT
I am very excited to start using the new features ColdFusion 10 introduces; however, the lack of support for the geography datatype is a major concern.
Comment by External U.
18979 | June 20, 2012 10:20:46 AM GMT
We can't upgrade to CF10 until this is resolved. We have been happily working with geography datatypes in CF9. GIS functionality is key to modern mobile web apps.
Vote by External U.
18993 | August 17, 2012 07:15:17 PM GMT
Suffering the same issues even after applying all updates up to 3rd April 2013. Any solutions? Guessing I'm missing something as the last entry here was 10 months ago...
Comment by External U.
18980 | April 03, 2013 04:33:22 AM GMT
We have logged an enhancement request with Data Direct.Here are the comments from Data Direct - "I discussed with our dev about this : The behavioral change was the result of the class-per-datatype work which we did. It was certainly unintentional to break this but it was never supported, filing the enhancement request was the right thing to do. We'll work to get it approved for inclusion in an upcoming release. "
Comment by Asha K.
18981 | April 26, 2013 04:12:07 AM GMT
Same problem with any of the versions of SQL Server that support spatial datatypes: 2008, 2008R2, 2012. Please fix!
Vote by External U.
18994 | July 22, 2013 04:20:06 PM GMT
This is a huge issue forcing us to create views on many tables as a work-around. This is a huge pain in the ass.
Vote by External U.
18995 | July 22, 2013 08:43:36 PM GMT
This issue has ultimately caused us to switch to C#.NET sadly. We are a GIS house and every table has GEO fields.
Comment by External U.
18982 | July 22, 2013 08:45:44 PM GMT
Is this issue going to be solved anytime soon?
Comment by External U.
18983 | July 24, 2013 02:43:00 PM GMT
Any progress on this? Is it fixed in CF11?
Comment by External U.
18984 | April 10, 2014 10:06:37 AM GMT
Should be a no-brainer to make current version of CF work with SQL Server 2014 field types. Please fix!
Vote by External U.
18996 | April 10, 2014 10:22:24 AM GMT
The annoying work around is to create views and not include geom columns.
Comment by External U.
18985 | April 10, 2014 10:23:09 AM GMT
Critical! Cannot upgrade from CF8 until this is fixed, or we'll have to abandon CF. Many modern applications use location based data which makes the geography datatype essential. It was added to SQL Server 6 years ago!
Vote by External U.
18997 | April 10, 2014 10:43:18 AM GMT
Elishia Dvorak of Adobe replied back to me on Twitter on this issue. Adobe engineers are still working with Data Direct to resolve this. In the meantime, she suggested downloading and trying Microsoft's free JDBC Type 4 driver instead of the DataDirect one that comes with ColdFusion.
Comment by External U.
18986 | April 11, 2014 02:32:40 PM GMT
We rely on the hierarchyId data type for complex analysis. We're reluctant to try a custom JDBC driver or change all of our usage of hierarchyId columns to call .toString().
Vote by External U.
18998 | May 30, 2014 09:18:48 AM GMT
Is this fixed?
Comment by External U.
18987 | June 02, 2014 03:27:10 PM GMT
This issue is fixed. This fix will be available with the upcoming update of ColdFusion 11.
Comment by Nimit S.
18988 | September 13, 2014 10:26:44 AM GMT