12 comments

Add a comment…

Sign in

prestine

Your email address

Check!

invalid email

(thinking…)

Reset

or sign in with

• 
• 

UserVoice password

Forgot password?

Create a password

Your name

I agree to the terms of service

Signed in as (Sign out)

Close

Close

Post comment Submitting...

• Brian commented  ·  April 19, 2012 1:54 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Spatial Data!

• Toby Harman commented  ·  April 1, 2012 9:41 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  All the SQL specific data types should be supported in EF if this is expected to be the ORM of choice.

  SQLVariant, XML, Hierarchy

  http://data.uservoice.com/forums/72025-ado-net-entity-framework-ef-feature-suggestions/suggestions/1051783-xml-data-type-support

  http://data.uservoice.com/forums/72025-ado-net-entity-framework-ef-feature-suggestions/suggestions/1124827-map-xml-sql-datatype-to-a-strongly-typed-serializa

• Murat BUDAK commented  ·  December 23, 2011 2:00 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  hierarchyid thumbup

• Murat BUDAK commented  ·  December 23, 2011 1:53 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  hierarchyid is important for the many large application. I am not thinking that who is not use hierarchyid in their applications. All the peoples are using their homemade solutions for the hierarchy. We need standardisation.

• Toby Harman commented  ·  November 16, 2011 10:27 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Almost Aaron, except that this one includes HierarchyId as well

• Aaron Shumaker commented  ·  August 16, 2011 1:19 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Duplicate of: http://data.uservoice.com/forums/72025-ado-net-entity-framework-ef-feature-suggestions/suggestions/1015351-support-for-spatial-types-and-spatial-query?ref=title

• Tony H. commented  ·  July 19, 2011 9:07 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Currently, SQL Server spatial types can only be supported by some intermediate hacks (e.g. using Triggers to convert and save basic types to spatial types, etc.). One has to evaluate the benefits of leveraging the EF along with the overhead of these hacks or is the the proper solution is to create a custom Data Access Layer. EIther way there is some heavy lifting. Thanks.

• Jean C. Nunez commented  ·  June 28, 2011 10:03 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Will be perfect if they released it on the next version...

• Courtney Mills commented  ·  May 21, 2011 5:15 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Can't wait till geometry and geography are supported.

• Rick Langel commented  ·  April 19, 2011 5:16 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  We need this.

• alYsa commented  ·  January 16, 2011 5:51 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  HierarchyID is critical, because it would allow seamless mapping of hierarchies represented in sql server to hierarchy on .Net side. I guess it would be best if it maps HierarchyID column to a collection of elements on .Net side.

• PAL commented  ·  September 13, 2010 10:47 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  HierarchyID