Closed isaacabraham closed 3 years ago
Also the geography
type has the same issue.
These types are deliberately not supported because AFAIK they have no simple .NET representation. You can easily skip these columns in the config file and work with the rest as if the skipped columns didn't exist. Here's part of the config reference for procedures. You can skip columns in procedures, scripts, table DTOs, and table scripts.
I believe that there is a Geography type in some of the MS SQL libraries - I believe it's this one. I think HierarchyId is also included in that.
Of course, that could potentially mean a dependency on that library for Facil, which you may not wish to do.
Thanks for the notice.
I'll leave these types unsupported for now until someone actually needs them.
Using the standard AdventureWorks sample DB (I think I got it from here), trying to run Facil gives the following error:
This appears to be a SQL type called HierarchyId.
Perhaps from a practical point of view, it would be best to have Facil simply warn and not generate tables that contains types that it does not support, but continue with the remaining ones? I'm thinking people would still benefit even if e.g. 90% of their DB could be generated and 10% had to be hand-rolled.