{"action":"created","issue":{"url":"https://api.github.com/repos/npgsql/npgsql/issues/600","labels_url":"https://api.github.com/repos/npgsql/npgsql/issues/600/labels{/name}","comments_url":"https://api.github.com/repos/npgsql/npgsql/issues/600/comments","events_url":"https://api.github.com/repos/npgsql/npgsql/issues/600/events","html_url":"https://github.com/npgsql/npgsql/issues/600","id":74956750,"number":600,"title":"Data Types Not Supported for the Target Entity Framework Version (EF 6.1.3)","user":{"login":"kmschaefer","id":8690531,"avatar_url":"https://avatars.githubusercontent.com/u/8690531?v=3","gravatar_id":"","url":"https://api.github.com/users/kmschaefer","html_url":"https://github.com/kmschaefer","followers_url":"https://api.github.com/users/kmschaefer/followers","following_url":"https://api.github.com/users/kmschaefer/following{/other_user}","gists_url":"https://api.github.com/users/kmschaefer/gists{/gist_id}","starred_url":"https://api.github.com/users/kmschaefer/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kmschaefer/subscriptions","organizations_url":"https://api.github.com/users/kmschaefer/orgs","repos_url":"https://api.github.com/users/kmschaefer/repos","events_url":"https://api.github.com/users/kmschaefer/events{/privacy}","received_events_url":"https://api.github.com/users/kmschaefer/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":10,"created_at":"2015-05-10T16:49:58Z","updated_at":"2015-05-25T16:57:49Z","closed_at":null,"body":"I'm unable to fully create an entity framework model when certain data types are in the targeted table. The table classes are created, but the unsupported data types are left out. Two examples are 'inet' and 'macaddr':\r\n\r\nError 6005: The data type 'inet' is currently not supported for the target Entity Framework version; the column 'mgmtip' in the table 'tablename' was excluded.\r\nError 6005: The data type 'macaddr' is currently not supported for the target Entity Framework version; the column 'mac' in the table 'tablename' was excluded.\r\n\r\nI've tried it with the 2.x and 3.x versions of Npgsql code in Visual Studio 2013 connecting to a Postgres 9.4 database running on Red Hat Linux 6.\r\n\r\nIf I connect to the database directly using just the Npgsql.dll reference in a console application, it correctly converts the data types to System.Net.IPAddress. It appears the problem is in the Npgsql.EntityFramework code."},"comment":{"url":"https://api.github.com/repos/npgsql/npgsql/issues/comments/105269421","html_url":"https://github.com/npgsql/npgsql/issues/600#issuecomment-105269421","issue_url":"https://api.github.com/repos/npgsql/npgsql/issues/600","id":105269421,"user":{"login":"roji","id":1862641,"avatar_url":"https://avatars.githubusercontent.com/u/1862641?v=3","gravatar_id":"","url":"https://api.github.com/users/roji","html_url":"https://github.com/roji","followers_url":"https://api.github.com/users/roji/followers","following_url":"https://api.github.com/users/roji/following{/other_user}","gists_url":"https://api.github.com/users/roji/gists{/gist_id}","starred_url":"https://api.github.com/users/roji/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/roji/subscriptions","organizations_url":"https://api.github.com/users/roji/orgs","repos_url":"https://api.github.com/users/roji/repos","events_url":"https://api.github.com/users/roji/events{/privacy}","received_events_url":"https://api.github.com/users/roji/received_events","type":"User","site_admin":false},"created_at":"2015-05-25T16:57:49Z","updated_at":"2015-05-25T16:57:49Z","body":"Wow, thanks @AEMPhil, it's nice to have someone who really knows GIS...\r\n\r\nThe proposal here is only how to expose PostGIS types via EF. As EF doesn't seem to support types outside its closed list, the only thing to do seems to be to expose those types that *are* supported in EF (probably covers the smaller SqlServer list), and to expose the rest as strings like any other type EF doesn't know. This is what @Emill is proposing.\r\n\r\nTotally unrelated to EF, we have a task to support PostGIS at the Npgsql type level, I.e. with full .NET types and binary send/receive (this is issue #529). This actually shouldn't be very hard, and if you feel like contributing it may be right up your alley :)\r\n\r\nOutside of type support, Npgsql doesn't really care about utility function support etc, that's really up to the user to use."}}