Reverse Engineer: Can we just scaffold string properties for xml, hierarchyid, geography, geometry, etc

[rowanmiller]

Some of these datatypes may just work with an implicit conversion to/from string. We need to investigate which ones work (or can work with minimal changes) and then update reverse engineer to scaffold a string property for them.

[bricelam]

@nteague22 It may require a few changes, but we should be able to set the parameter type using the SqlServerTypeMapper.

[nteague22]

Excellent, I really am impressed with the work you guys produce and the team as a whole! Even in beta, EF7 makes my life easier on running ETL and other data migratory operations

[wangkanai]

How is issue going? I still that the https://github.com/aspnet/EntityFramework/blob/dev/src/EntityFramework.MicrosoftSqlServer/Storage/Internal/SqlServerTypeMapper.cs is unchanged.
Hoping to see this feature add by rc1 :)

[bricelam]

@wangkanai Have you tried manually adding the properties to your model?

[wangkanai]

@bricelam Do you mean like mapping a object property System.Data.Spatial to Spatial Data Types in demo application? No 😄, don't know where to start, still studying your codebase.
Or add RelationalTypeMapping to your SqlServerTypeMapper.cs class?

private readonly RelationalTypeMapping _geography = new RelationalTypeMapping("geography");
private readonly RelationalTypeMapping _geometry = new RelationalTypeMapping("geometry");

*Did some testing, and it go very deep into the core * 😅 skiming guess, its going to take a few 100 manhours base on my skills

[gitmar]

Fail to try scaffolding a xml sql datatype and fail to manually add the property in my model. Dont know how to do that manually.
Could not find type mapping for column 'dbo.mytable.myxmlcolumn' with data type 'xml'. Skipping column.

[lajones]

Have checked in a fix for xml columns (@gitmar this should solve your problem above) - commit a8b185f.

[lajones]

Support for hierarchyId and spatial types is more complicated and not yet supported by the update and query pipelines. So closing this in favor of #365 (which tracks hierarchyid) and #1100 (which tracks support for spatial types).